https://bz.apache.org/bugzilla/show_bug.cgi?id=69631
--- Comment #3 from sephir...@sephiroth-j.de --- The affected application is a jax-ws Soap service and I think the exception occurs when opening the endpoint servlet (that one showing the endpoint classes and wsdl, com.sun.xml.ws.transport.http.servlet.WSServlet I think). So it's a simple http get request. The server shows the 404 page when it happens. It's also definitely not a load issue. We use the endpoint servlet as health/liveness endpoint in kubernetes and we observed the issue on idle instances as well. I have not checked whether the timestamps for those exceptions that are logged in Splunk match to the timestamps of the liveness checks but I am quite sure they do. If you need more information, please be patient as I can't provide you with more details for the next two weeks. -- 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
