tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18698] New: - Exception message in JNDI realm is not "Socket closed" on different ldap implementations
Date Fri, 04 Apr 2003 08:28:44 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18698>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18698

Exception message in JNDI realm is not "Socket closed" on different ldap implementations

           Summary: Exception message in JNDI realm is not "Socket closed"
                    on different ldap implementations
           Product: Tomcat 4
           Version: 4.1.24
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: Armin.Haaf@mercatis.de


JDNIRealm.java:

public Principal authenticate(String username, String credentials) { 
...
// If not a "Socket closed." error then rethrow.
if (e.getMessage().indexOf("Socket closed") < 0)                    
    throw(e);
                

Socket closed is not the message I got, but "connection closed". It is not a
good way to check the message of a exception and react on it. Please just remove
this two lines of code and try connect again, this will fix the problem

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message