No, there are no errors in catalina.out. We did set the LD_ASSUME_KERNEL=2.2.5 about 10h ago and so far everything looks OK. But it's still too early to say if it is a fix to our problem.
Sondre -----Original Message----- From: Martin Gainty <[EMAIL PROTECTED]> Sent: 15. desember 2005 16:43 To: Tomcat Users List Subject: Re: Tomcat stops answering requests my understanding is that the tomcat connectors can be paused are there any errors showing in catalina.out? M- ----- Original Message ----- From: "Dov Rosenberg" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Thursday, December 15, 2005 8:26 AM Subject: Re: Tomcat stops answering requests >I recently have been chasing similar demons. My logs showed something like > > INFO: Paused Coyote HTTP/1.1 on http-7001 > > I did some searching and someone suggested upgrading my JVM. We were using > 1.4.2_05 and I have updated to 1.4.2_08. So far so good. > > > Any other ideas? I am open for suggestions!! > > > > > On 12/15/05 2:42 AM, "Sondre Engell" <[EMAIL PROTECTED]> > wrote: > >> Hi. >> >> We are experiencing some problems with our Tomcat. We are currently >> running >> Apache 2.0.54, Tomcat 4.1.30, Axis 1.2.final on RedHat 9.0 with kernel >> 2.4.27. >> >> We have some web-services deployed under Axis and these services become >> unavailable during normal operation. It seems that this occurs because >> Tomcat >> stops answering requests on port 8080 (the Apache-Axis diagnostic web >> page >> (<http://127.0.0.1:8080/axis>) becomes unavailable). >> >> After examining the Tomcat log files the only suspicious entries we found >> was >> this exception that occurs regularly: >> >> 2005-12-12 12:47:04 StandardManager[/axis] Session event listener threw >> exception >> java.lang.IllegalStateException: getAttribute: Session already >> invalidated >> at >> org.apache.catalina.session.StandardSession.getAttribute(StandardSession.java: >> 953) >> at >> org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSession >> Facade.java:171) >> at >> org.apache.axis.transport.http.AxisHTTPSessionListener.destroySession(AxisHTTP >> SessionListener.java:43) >> at >> org.apache.axis.transport.http.AxisHTTPSessionListener.sessionDestroyed(AxisHT >> TPSessionListener.java:72) >> at >> org.apache.catalina.session.StandardSession.expire(StandardSession.java:658) >> at >> org.apache.catalina.session.StandardSession.expire(StandardSession.java:607) >> at >> org.apache.catalina.session.StandardManager.processExpires(StandardManager.jav >> a:793) >> at >> org.apache.catalina.session.StandardManager.run(StandardManager.java:870) >> at java.lang.Thread.run(Thread.java:534) >> >> It looks like Catalina tries to call getAttribute on a session it has >> already >> destroyed. Can this bring Tomcat to stop answering requests. Since the >> exception says that the session is already invalidated I would believe >> that >> the session is indeed destroyed. If not, could this cause a starving of >> free >> sessions, and thus bring Tomcat to a halt? >> >> I have seen some posts proposing to use: >> export LD_ASSUME_KERNEL=2.x.x >> >> Can that be a solution? As stated above we use RedHat 9.0 with kernel >> 2.4.27 >> what kernel version should we use in the export? >> >> We are really lost on this one and if anyone have any idea of what can >> cause >> Tomcat to stop answering requests we would very much like to hear them. >> >> Regards >> >> Sondre >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > -- > Dov Rosenberg > Conviveon/Inquira > Knowledge Management Experts > http://www.conviveon.com > http://www.inquira.com > > > > > --------------------------------------------------------------------- > 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]