You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/06/20 13:23:33 UTC
DO NOT REPLY [Bug 19864] -
JNDIRealm NullPointerException / CommunicationException when Context Closed
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=19864>.
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=19864
JNDIRealm NullPointerException / CommunicationException when Context Closed
------- Additional Comments From paal@objectbox.com 2003-06-20 11:23 -------
When I encouter these problems the e.getMessage() returns "simple bind failed:
10.1.1.3:389", while e.toString()
returns "javax.naming.CommunicationException: simple bind failed:
10.1.1.3:389. Root exception is java.net.SocketException: Socket closed".
I replaced e.getMessage() with e.toString(), and now it works as expected and
attemptes a second login:
if (e.toString().indexOf("Socket closed") < 0)
throw(e);
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org