I'm late to the party. But how about trying the following ...
1) Add a filter which runs first and logs the request. This WILL have a
performance impact - but a non-running application is a tad bit slower
than writing each request to disk. With luck - this may call out a class
of (or single) urls which can then be examined to see if you can
reproduce the app death.
2) Run all the code in the webapp through a decompiler and look for
System.exit() - then for all the spots where System.exit exists - then
see if that piece of code might be called. [warning: Depending on who
wrote the code, or the libraries used - this may violate some licenses.]
-Tim
On 12/8/2010 5:37 PM, Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Victor,
On 12/6/2010 3:47 PM, Victor Kabdebon wrote:
Your Linux may also be involved. If you have some weird configuration of
your system, it may kill/shutdown some services / applications.
If it's the Linux OOM killer, you should get a syslog message about it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
