Problem: Java Viewer fails to display all features coming from a FeatureServer map service
When using a Java client, such as the ArcIMS Java Viewers or ArcExplorer, to access a FeatureServer-based map service, some or all features from one or more layers fail to draw on the map canvas. The affected layers and features appear to change randomly while panning or zooming.
"HTTP Return Code: 403" is seen intermittently in the Java Plug-in Console.
This problem is often caused by a lack of available client connections on the Web server. The ArcIMS Java Viewers and ArcExplorer send separate HTTP requests to the Web server for retrieving data from each layer present in the map. If all available connections on the Web server are occupied, the Web server sends an HTTP 403 (Forbidden) back to the requesting client.
Solution or Workaround
To resolve this problem increase the number of concurrent connections allowed by the Web server. Consult the Web server's documentation for details on configuration.
Depending on the Web server and operating system, increasing the Web server connection limit may constitute a violation of the Web server's license agreement. Please contact the Web server software manufacturer's support facility if there are questions on the license agreement.
- An alternative approach is to reduce the number of layers visible at one time. To do this, set scale-dependent visibility so that some layers turn off when other layers turn on as the user zooms in and out.
- Another alternative is to reduce the number of layers is to combine several of the datasets together into a single dataset so that it can display as a single layer. Then set up valuemap renderers to display different groups of features differently if desired.