Send Tomcat a QUIT (11) signal on Unix, or control/break (run it interactively) on Windows. This will cause the VM to dump all thread stacks.
If you don't like Tomcat, you can always shell out some big bugs for a commercial application server. For some even bigger bucks you can get commercial support. I can tell you it's unlikely you'll get a warm reception from the very people who can help you given the current tone of your postings. FWIW, I have deployed 4 commercially successful, long-running applications under various versions of Tomcat. For what you pay for it, I find it works tremendously well. Like most open-source projects, the documentation is below what you would get in a commercial product, but that's because developers enjoy writing code, but not docs. Still, the information is out there if you look around a bit. Tim -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Nowak Sent: Tuesday, February 28, 2006 1:32 PM To: users@tomcat.apache.org Subject: Re: Sad: Tomcat 5.5.x crashes almost every single day. Peter Crowther <[EMAIL PROTECTED]> wrote: > > Have you tested it for deadlocks that would cause hangs? > [...] Profile your application. What's eating memory? > Get a thread dump when your application hangs. Is anything > deadlocked? What? Where? How? http://www.google.com/search?hl=pl&q=%22thread+dump%22+site%3Atomcat.apache. org http://www.google.com/search?hl=pl&q=profile+application+site%3Atomcat.apach e.org -- T. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
