Peter <> changed:

           What    |Removed                     |Added
             Status|NEEDINFO                    |NEW

--- Comment #4 from Peter <> ---
Using Felix's patch, letting the tomcat warm up with some ok requests and both
auth servers online, then taking the first down, then doing a request (to our
regular app, or the dummy), it takes 6s to fail and says:

<!doctype html><html lang="en"><head><title>HTTP Status 401 –
Unauthorized</title><style type="text/css">h1
body {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;}
b {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} p
a {color:black;} {color:black;} .line
Status 401 – Unauthorized</h1><hr class="line" /><p><b>Type</b> Status
Report</p><p><b>Description</b> The request has not been applied because it
lacks valid authentication credentials for the target resource.</p><hr
class="line" /><h3>Apache Tomcat/8.5.16</h3></body></html>

And then subsequent requests work fine. (but the dummy always says the above,
so I guess you can't test that)

Doing the failure the other way around works the same.

If I set the timeout to 500 in the server.xml, it takes 1s instead.

So the timeout works great, but it doesn't seem to fall back to the
alternate/connection URL. So I think the patch is good, but incomplete.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to