Hi all,
I now have a bit more information on this.
The problem arises, when you have configured a single LDAP connection
(no pooling) and the a naming exception is thrown (for example) in
JNDIRealm#getPrincipal (for example line 2242 in current main). In that
location we hold a lock while bee
Hi all,
yesterday, we had a Tomcat, that would be unresponsive for about twenty
minutes on every full hour. The cause was a long running scheduled job
that used the /last/ available connection of the 200 default
connections. All other connections were waiting to lock the single LDAP
connectio
