> From: Karim Zibari [mailto:[EMAIL PROTECTED] > Subject: Re: Tomcat reloading > > how about if my web app ran out of memory or it made too many > database connections or (as my hosting compnay suggests) that > my web app was to get stuck in loop and render the processor > non-responsive to other requests.?
Again, it's an OS flaw to allow one process to preempt all others, even if there is only one CPU on the server (which is unlikely, these days). Locking out a ping response is nearly impossible, since that requires only trivial resources. Your hosting company should be able to supply a thread dump of your process, if that's the only thing stuck on the server. Likewise, they should be able to definitively determine what's going on; some unfortunately, are understaffed and underequipped, and simply try to push problems off on someone else. If you were running out of memory, you would see exceptions in the log. You could also turn on -verbose:gc if you want to prove that memory is not an issue. You could also try a tracert to the server, and see at what point in the route the responses stop. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
