Yoav Shapira wrote:
Hola,
On 3/13/07, Phillip Thurmond <[EMAIL PROTECTED]> wrote:
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 a
Hola,
On 3/13/07, Phillip Thurmond <[EMAIL PROTECTED]> wrote:
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 dependen
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 lik
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 al
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 Tomc
