This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
It seems that when an exception falls through to Tomcat that the Tomcat instance (and all installed apps) stop functioning. Is there a way to setup Tomcat to continue to run after an application exception or at the very least have Tomcat restart when it stops responding?
It seems that when an exception falls through to Tomcat that the Tomcat instance (and all installed apps) stop functioning.
No, at least for exceptions occurring in a normal request Thread.
Once the exception has fallen all the way through to the service method it gets reported but Tomcat remains able to accept new requests.
If this is happening to you, some unusual circumstances must exist. What do you mean by "stop functioning"?
How are you starting Tomcat?
Mention Java version, Tomcat version and operating system to save time.
Li Jia Long
Joined: Apr 04, 2007
Thank you for the reply. We are using the latest 5.5.23 Tomcat release with Java 1.5.10. We are starting up using the startup.sh script to start Tomcat.
I suspect it may be a servlet behaving badly. When I say that the installed apps stop functioning, requests to the server never return. The web browser never gets a response until the browser just gives a timeout. The odd thing is that once the error falls through on one of the servlets all of the installed servlets on the server behave the same way by not responding.
Author and all-around good cowpoke
Joined: Mar 22, 2000
Right off hand I would say you have one or more request Threads stuck in a loop and consuming all the CPU time.
Your first post mentioned an Exception - is that speculation or did one actually get reported?