> From: Jerry Malcolm [mailto:techst...@malcolms.com] > Subject: Webapp killing entire Tomcat process
> But in my opinion, no matter what happens in the code, TC shouldn't > completely die, correct? Nope, it's all one process, and any thread can take it out. Running with a security manager reduces the chance, but doesn't preclude it. Simple silliness such as calling System.exit() will also stop everything. > I guess my question is, do you have any suggestions for anything my code > might do that could kill the process? At least it might give me a start > at what to look for. The first step is to stop running Tomcat as a service, and instead start it from a command prompt using the startup.bat script. You can also attach a debugger this way and watch what's going on, set breakpoints, etc. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
