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: http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/pool.html 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? Thanks, Kris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
