This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have a Java Application running on Tomcat. Twice now, I will go to call a servlet during a period of time when everything was working fine and get a HTTP Status 500: No Context Configured To Process This Request.
When I check the processes running there is no Java process running.
A restart of Tomcat fixes it.
Is something not configured correctly? How can this happen during processing? Could a process hogging too much memory cause this?
[ October 05, 2005: Message edited by: Luke Shannon ] [ October 05, 2005: Message edited by: Luke Shannon ]
This means you are running Tomcat in isolation rather than piggy-backing it to Apache.
Joined: Sep 30, 2004
I am using mod_jk to forward request from Apache to Tomcat, so I guess the answer is no.
I guess what I am looking for is the best way to go about trouble shooting this. It happens intermittently and the logs aren't telling me anything. Could this be a mod_jk config issue? Could a very heavy Java process being repeated cause Tomcat to crash?