DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43790>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43790
Summary: concurrent access issue on TagHandlerPool
Product: Tomcat 6
Version: unspecified
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: michael.mao@achievo.com
when doing performance test, i found the concurrent acess lock issue about JSP
tag. Many threads are waiting for TagHandlerPool object, such as
TagHandlerPool.reuse, TagHandlerPool.get.
In TagHandlerPool and PerThreadTagHandlerPool class, object pool was used, but
its synchronization cause the thread waiting/lock issue when a lot of JSP tags
are using. Later, I test a ThreadLocal based TagHandler object instead of
TagHandlerPool, the response time was reduced to 5s from 30s against 50
concurrent user.
As a suggestion, please remove object pool to replace with simple ThreadLocal
solution. The same issues exist both Tomcat 5.X and 6.0.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
|