https://bz.apache.org/bugzilla/show_bug.cgi?id=61313
--- Comment #6 from Peter <peter.malo...@brockmann-consult.de> --- Created attachment 35151 --> https://bz.apache.org/bugzilla/attachment.cgi?id=35151&action=edit second possibly hacky patch, includes Felix's patch Here's another possibly hacky patch. This one looks less hacky, but it only covers the one place where the exception I observed happens. I chose that place because it is the first call of a protected method in the stack; the others before are public. And I don't know if it could loop forever, or pointlessly retry when there is another kind of exception which is also a NamingException (this one is a read timeout... I don't know what else there is). With this patch, the problem is fixed in my testing... a failed server that was already in a previous context will cause only a delay about 0.5s plus the readTimeout. And both servers down will result in the "HTTP Status 401 – Unauthorized" error and delay will also be about 0.5s plus the readTimeout. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
