Bug
The Java ADF spawns off five threads for each web session, which don't expire until the web session expires. This makes the Java ADF not scalable enough to handle large numbers of simultaneous users.
| Bug ID Number | NIM009880 |
|---|---|
| Submitted | June 23, 2007 |
| Last Modified | June 5, 2024 |
| Applies to | No Product Found |
| Version found | 9.2 |
| Program language | Java |
| Status | Will Not Be Addressed |
Additional Information
No Public ExplanationWorkaround
When multiple resources are requested, the Java ADF requests those resources in parallel for better performance. Each parallel request requires its own thread. We believe this makes the Java ADF more scalable since requests are handled faster and thus you make better use of your existing hardware. However, it is possible to reduce the number of threads used by the application which will result in slower performance. This method below will set the thread pool size:<a href="http://edndoc.esri.com/arcobjects/9.2/Java/api/adfwebcontrols/com/esri/adf/web/data/WebContext.html#setThreadPoolSize" target="_blank">http://edndoc.esri.com/arcobjects/9.2/Java/api/adfwebcontrols/com/esri/adf/web/data/WebContext.html#setThreadPoolSize</a>(int)Steps to Reproduce
Bug ID: NIM009880
Software:
- No Product Found
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App