tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kris Easter <>
Subject PooledJNDIRealm
Date Tue, 16 Oct 2012 20:41:16 GMT

We are using the delivered JNDIRealm class for LDAP authN in Tomcat
7.0.29 but we're running into some problems when the back end LDAP is a
little slow (another issue being addressed separately) and having
threads stack up and timeout.  A thread dump shows we end up with a lot
of blocked threads, that timeout since we have Apache in front of
Tomcat, that seem to be stuck on the synchronized authenticate method.

We've rewritten a PooledJNDIRealm using this pooling:

the rewritten version is just the original JNDIRealm with minimal
changes to make it work with the pooling and removing the
synchronization.  Proof of concept testing seems to work but it has yet
to be subjected to a heavy load test.

Are there any gotchas around this approach?  I'm not seeing any unit
tests for JNDIRealm, and we're only using part of it, are any regression
tests available?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message