Tomcat does this to me periodically, but it almost always involves some
problematic code I'm running.
The only way I know of debugging it is to search your access logs for the last
pages that have been accessed and work backwards with log entries in your code
to see where the server is crashi
I've run into a problem with this. If a session times out, and someone comes
back to post say a wiki page that they've been working on, it causes a problem.
Is there any way of dealing with this? Logging people off automatically
obviously won't work, because that's what's effectively happenin
Thanks so much for everybody who replied to this. I apologize for not
replying/thanking sooner, but I have been trying to get this thing working.
Unfortunately I'm having only marginal success. I'm thinking maybe there's
something very fundamental that I'm not getting.
Here's where I'm at:
I'm trying to list the applications in the manager app. It was working before,
but now all of a sudden it has stopped. It was working before, but I added an
app and it stopped working. I remove the app and it still doesn't work. I
clean the work space for the manager app and it still doesn't
I'm trying to rework my server.xml file so that the context info can be
reloaded without restarting the entire server. As far as I can tell this
involves putting the context information in a file outside of server.xml. I've
read that META-INF/context.xml only works with WAR files, and I don't
