Locking in JaasSecurityManager.isValid

[parmarsanjay]

In our performance test we are seeing that threads are getting blocked at

"Ajp13Processor[8009][25]" daemon prio=5 tid=0x64097100 nid=0x79c waiting for monitor entry [65e4f000..65e4fd88]
at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:238)
- waiting to lock <0x26167fd0> (a org.jboss.security.plugins.JaasSecurityManager)
at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:219)
at org.jboss.web.catalina.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:291)
at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:173)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:526)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)


Any idea why ? I looked the source of isValid method and it's synchronized method.

[parmarsanjay]

We are using JBoss 3.2.1.

[starksm64]

Its a known bottleneck that will be addressed in the 4.0.3 release.

[parmarsanjay]

Thanks Scott for the quick around. There is no way to fix this issue in JBoss 3.2.x ? Is there a work around ?

We are telling our customers to go-live on this release. This is really critical for us in Production enviornment.

[starksm64]

No workaround exists.