https://bz.apache.org/bugzilla/show_bug.cgi?id=65411
Bug ID: 65411
Summary: NamingException in JDNIRealm.getPrincipal(String
username, GSSCredential gssCredential) ends in
locked-up realm
Product: Tomcat 9
Version: 9.0.39
Hardware: All
OS: All
Status: NEW
Severity: regression
Priority: P2
Component: Catalina
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: -----
A NamingException during JDNIRealm.getPrincipal(String username, GSSCredential
gssCredential) leads to a locked up realm. Which leads to tomcat locking up.
Similar to the fix for Bug 65033
(https://bz.apache.org/bugzilla/show_bug.cgi?id=65033), the second catching of
the NamingException should also close the connection and unlock the
singleConnectionLock.
It seems that the connection used to be closed, but with 9.0.39 and this commit
https://github.com/apache/tomcat/commit/95658dfd868216db0773c38aad8eebf544024b09?branch=95658dfd868216db0773c38aad8eebf544024b09
the close(connection) is not called anymore.
Corresponding PR: https://github.com/apache/tomcat/pull/430
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
