I just want to confirm if what I'm seeing is the expected behavior....
While running load tests, I see each user locking a thread for
com.sun.enterprise.web.portunif,PortUnificationPipeline,
eg: 400 users logging in and out, I will see these 396 of these in
either BLOCKED or WAITING state:
"httpSSLWorkerThread-8080-67" daemon prio=3 tid=0x0000000004fba000
nid=0xd9e in Object.wait() [0xfffffd7e9823a000..0xfffffd7e9823aa10]
java.lang.Thread.State: *BLOCKED * (on object monitor) at
java.lang.Object.wait(Native Method) - waiting on
<0xfffffd7ebc020f60> (a
*com.sun.enterprise.web.portunif.PortUnificationPipeline*) at
java.lang.Object.wait(Object.java:502) at
com.sun.enterprise.web.connector.grizzly.LinkedListPipeline.getTask(LinkedListPipeline.java:291)
- locked <0xfffffd7ebc020f60> (a
com.sun.enterprise.web.portunif.PortUnificationPipeline) at
com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:107)
Locked ownable synchronizers: - None