DO NOT REPLY [Bug 6990] - Catalina 4.0.2 hangs after a few days

2003-09-19 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990

Catalina 4.0.2 hangs after a few days

[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|tomcat- |[EMAIL PROTECTED]
   |[EMAIL PROTECTED]  |
 Status|CLOSED  |NEW

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 6990] - Catalina 4.0.2 hangs after a few days

2002-04-22 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990

Catalina 4.0.2 hangs after a few days





--- Additional Comments From [EMAIL PROTECTED]  2002-04-22 20:22 ---
cool, thanks a lot for the info. I have a script that finds these spinning httpd
processes and terminates them, it's a hack but it works wonderfully.  Looking
forward to future tomcat 4.0.x releases

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




DO NOT REPLY [Bug 6990] - Catalina 4.0.2 hangs after a few days

2002-04-17 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990

Catalina 4.0.2 hangs after a few days





--- Additional Comments From [EMAIL PROTECTED]  2002-04-17 21:12 ---
I get something similar.  I'm using Catalina 4.0.2 with Ajp13Connector/mod_jk
compiled from Tomcat Connectors 4.0.2_1, using apache 1.3.22 to serve non-jsp
pages.  We are running are production site off the following setup, but
occasionally a java/httpd pair will start spinning indefinately.  Curious about
what was causing this, I took a stack dump using killall -QUIT java and looked
up the spinning threads.  This revealed the following thread which seemed to be
hanging above request.getParameter(String paramname). Let me know if you need
more info, or suggestions on working around the problem.

Ajp13Processor[8009][9] daemon prio=1 tid=0x0x828a1c0 nid=0x7e33 runnable
[5437f000..5438086c]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:116)
at org.apache.ajp.Ajp13.readN(Ajp13.java:429)
at org.apache.ajp.Ajp13.receive(Ajp13.java:469)
at org.apache.ajp.RequestHandler.refillReadBuffer(RequestHandler.java:712)
at org.apache.ajp.RequestHandler.doRead(RequestHandler.java:655)
at org.apache.ajp.Ajp13.doRead(Ajp13.java:354)
at org.apache.ajp.tomcat4.Ajp13InputStream.read(Ajp13InputStream.java:99)
at
org.apache.catalina.connector.HttpRequestBase.parseParameters(HttpRequestBase.java:644)
at
org.apache.catalina.connector.HttpRequestBase.getParameter(HttpRequestBase.java:674)
at
org.apache.catalina.connector.RequestFacade.getParameter(RequestFacade.java:160)
at org.apache.jsp.memberLogin$jsp.login(memberLogin$jsp.java:59)
at org.apache.jsp.memberLogin$jsp._jspService(memberLogin$jsp.java:500)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
at com.ee.servlet.RedirectJspServlet.service(RedirectJspServlet.java:43)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at com.ee.servlet.HandleJspServlet.invoke(HandleJspServlet.java:77)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at

DO NOT REPLY [Bug 6990] - Catalina 4.0.2 hangs after a few days

2002-03-08 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990

Catalina 4.0.2 hangs after a few days

[EMAIL PROTECTED] changed:

   What|Removed |Added

  Component|Catalina|JK/AJP Connector
Version|4.0.2 Final |4.0.3 Final



--- Additional Comments From [EMAIL PROTECTED]  2002-03-08 17:19 ---
It is very hard to use this kind of bug report as is, since it doesn't specify
much information except the fact that TC is hanging.
For example, you should precise the workload and the type of webapps used
(servlets, JSPs, EJBs, ...), suspect errors which may end up in the logs.

Also, did you try to test your server with ab ? Can you reproduce the problem
just by hammering the server for some time ?

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




DO NOT REPLY [Bug 6990] - Catalina 4.0.2 hangs after a few days

2002-03-08 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990

Catalina 4.0.2 hangs after a few days





--- Additional Comments From [EMAIL PROTECTED]  2002-03-08 17:45 ---
Well, Remy, this bugreport is so laconic because not too much can be seen from 
what's happening. There's our website, modest load (30-60 concurrent sessions, 
I don't exactly know how many concurrent users). 

I tried to stress the application a bit (opening 4-5 browsers, requesting pages 
randomly). There was no problem. My suspicion is that time is a factor here 
that matters somehow. 

What I noticed in each case was that there is always exactly one thread (linux 
process) which cannot be killed. It seems that memory is not eaten up, CPU is 
free, so it indicates that the process in question simply waits for something. 
But then why this hangs the whole server?

cheers,
János

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




DO NOT REPLY [Bug 6990] - Catalina 4.0.2 hangs after a few days

2002-03-08 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6990

Catalina 4.0.2 hangs after a few days





--- Additional Comments From [EMAIL PROTECTED]  2002-03-08 18:22 ---
Could you use ab to stress test the site (it's included in the Apache HTTPd
binaries), and see if you can reproduce the problem using that ?
Are all the logs empty of useful info ? (in particular, catalina_log)
Without a reliable way to reproduce it, this will be very hard to fix, I'm afraid.

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]