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.
上次发布: August 25, 2014No Product Found
漏洞 ID 编号
NIM009880
已提交
June 23, 2007
上次修改时间
June 5, 2024
适用范围
No Product Found
找到的版本
9.2
编程语言
Java
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
No Public Explanation
解决办法
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)