We had the same problem w/ TC 4.1.27, sun jvm 1.4.2 and redhat 9. The thing wouldn't work for more than about 12 hours. IMHO, there are some fundamental problems with tomcat as of late. Hate to say it but we solved the problem by throwing away tomcat and using jetty! We are very pleased so far. Jetty is very fast and about 1/3 the memory footprint.
Good luck. -----Original Message----- From: Noam Camiel [mailto:[EMAIL PROTECTED] Sent: Monday, April 07, 2003 5:09 AM To: Tomcat Users List Subject: Re: tomcat jitters, then hangs - please help On Thursday, October 09, 2003 10:39 PM "Remy Maucherat" <[EMAIL PROTECTED]> wrote: > It is very surprising that the connector will manage to exit the accept > loop without logging some kind of error (which would be in catalina.out, > rather than in the main logs). Do you see some stack trace originating > from the PoolTcpEndpoint or ThreadPool classes ? There were no logs indicating this, and actually, after the server started there are no other logs appearing in catalina.out > No idea at this point. Most (all) such reports were for RH 9. All also > mention a period of about a day before an incident. Thanks, let me know if there's any news. Regards, Noam ----- Original Message ----- From: "Remy Maucherat" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Thursday, October 09, 2003 10:39 PM Subject: Re: tomcat jitters, then hangs - please help > Noam Camiel wrote: > > On Thursday, October 09, 2003 5:11 PM "Ryan Lissack" > > <[EMAIL PROTECTED]> wrote: > > > >>Hi Noam, > >> > >>We have experienced similar problems. You will notice in the thread dump > >>that there is no thread from the connectors thread pool waiting on an > >>accept > > > > > > I see your what you mean, I compared the thread dump to a "good" dump when > > the server is operational and there indeed I found a thread from the > > connectors thread pool waiting on accept: > > > > 3XMTHREADINFO "http80-Processor24" (TID:0x100688E0, > > sys_thread_t:0x87810C0, state:R, native ID:0x41CCCF40) prio=5 > > 4XESTACKTRACE at java.net.PlainSocketImpl.socketAccept(Native > > Method) > > > > This does not appear to exist in the "bad" dump. > > It is very surprising that the connector will manage to exit the accept > loop without logging some kind of error (which would be in catalina.out, > rather than in the main logs). Do you see some stack trace originating > from the PoolTcpEndpoint or ThreadPool classes ? > > >>What OS are you on, RH9?? > > > > Yes, Im on RH9. > > > > Any ideas why this could happen? could it be some system resource limit? > > Is your application an intensive app? My application is not an intensive one > > and the hangs occur hours after i start the server (usually a day later). > > No idea at this point. Most (all) such reports were for RH 9. All also > mention a period of about a day before an incident. > > -- > xxxxxxxxxxxxxxxxxxxxxxxxxxxxx > Re'my Maucherat > Senior Developer & Consultant > JBoss Group (Europe) Sa`RL > xxxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
