DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33774>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33774 ------- Additional Comments From [EMAIL PROTECTED] 2005-03-24 18:10 ------- Right, but when handling the said communication exception: // If contains the work closed. Then assume socket is closed. // If message is null, assume the worst and allow the // connection to be closed. if (e.getMessage()!=null && e.getMessage().indexOf("closed") < 0) throw(e); Here, the text is: exception performing authentication javax.naming.CommunicationException: Connection reset [Root exception is java.net.SocketException: Connection reset]; remaining name 'ou=ou=users,dc=company,dc=com' So no "closed", which means there won't be any retry. This type of hack is bad: we should just retry once anyway. I'm changing that in 5.5.x. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
