-----Original Message-----
From: Halfmann, Klaus [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 05, 2002 3:54 PM
To: Tomcat Users List
I could think about the following reasons:
a) a hard crash of the Java VM (may happen when using native
code)
b) Some code calls System.exit()
c) You get to many OutOfMemory Exceptions eventually killing the
VM
----------------------------------------------------------------------
Wat are native code? I really do not noe would u mind explaining?
In case of a) there should be either a core dump or at least some System
log. Try starting Tomcat in a console of its own and look what happens.
----------------------------------------------------------------------
Do u mean start in command prompt?
b) Can be fighted by Starting Tomcat with a Security Manager prohibiting
a call to System.exit(). Eventually you can trace the culprit then
by looking for the SecurityException
----------------------------------------------------------------------
argh.... again.... how do i configure the security manager....
c) Monitor the Resource Usage of the Application and the logs ....
In General setting the Debug level in the server.xml may give you
some hints (For a proper shutdown the destroy() methods of Servlets)
should be called. Hope you have enough space on your devices to log
away 4-5 hours ...
------------------------------------------------------------------------
How do i set my debug level??? argh... im a real newbie... pls help...
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
