On 12/29/24 3:34 PM, Christopher Schultz wrote:
Do you have a capture of the exact error? Handshake errors typically include at least a terse amount of detail.
On the client side, Chrome was singularly uninformative about the error. With New Year's Eve and New Year's Day coming up, I might be able to run the test again, and capture the exact browser message. If there's any non-obvious place for me to look for underlying problems, please tell me.
I also looked at the catalina.out from the timeframe in which I ran my test, and there is literally nothing in there between the message that our webapp is up, and the message that I'd initiated a shutdown to switch back to the "good" server.xml.
As a programmer, I have had to deal with customers who complain about our terminal-based DB2/400-access utility crashing, but only giving us the final error message issued by our product, while ignoring what could be half a dozen or more joblog messages leading up to it, so I know where you're coming from here. But at this point, I've tried to find everything I'd be asking the customer to produce, and come up empty.
-- JHHL --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
