A change was made to the JNDI lookup in 3.0.4 that retries lookup ops due
to connection errors. This was an attempt to workaround problems with
windows tcp stack not handling accept backlogs well.

The problem is that this broke the ability to reconnect to a server that has been
restarted because the ConnectionException that was being caught in the retry
loop was not thrown if the retries were exhausted. The bad server reference in
the cache was not flushed and lookups to the restarted server always returned
null instead of throwing an exception. In general you need to make sure that
you test the exception path still works when you attempt to change its handling.

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx


-------------------------------------------------------
This sf.net email is sponsored by: Are you worried about 
your web server security? Click here for a FREE Thawte 
Apache SSL Guide and answer your Apache SSL security 
needs: http://www.gothawte.com/rd523.html
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to