Remy Maucherat wrote:
Phillip Thurmond wrote:
I'm running some performance tests on JBoss 4.0.5. I'm seeing some
contention inside Tomcat on ApplicationContext.getAttribute(). With
a load of 200 threads, I often see over 150 "waiting to lock"
messages on the attributes object. It looks like this contention has
already been fixed in Tomcat 6 using the Java 5 concurrent objects.
Could this be fixed in Tomcat 5.5 using some other concurrency libs
(oswego)?
Simple question, simple answer: no (reason: no additional dependency).
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This is a bug. It significantly hinders scalability under certain
workloads, and it should be fixed. As you are aware, there are many
solutions (Read/Write lock, partitioned hashmap, etc..) that do not
involve an additional dependency.
--Phillip
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
