I have a connector problem as well, just a bit different. I am using a version of the JK connector that I used to use with tomcat 3.2.4 and had no problems. After switching to Tomcat 4.1.16 and above, I have been having problems serving pages. It seems to be related to the timeout attribute in the coyote connector definition in server.xml. Once in a while, I get the following error, resulting in the page not being able to display to the client.
[INFO] ChannelSocket - -server has been restarted or reset this connection This happens in about one out of every thousand clicks, but I don't know why. If I set the timeout attribute to something like 20000 instead of -1 for coyote in server.xml, it happens in about one out of every five clicks. I thought upgrading to a new connector such as coyote would help, but now it sounds like I should avoid that as well. Nobody has ever mentioned this problem anywhere before, does anyone have any ideas at all? Brandon -----Original Message----- From: Luc Foisy [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 19, 2002 9:04 AM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: 4.1.17 Problems - Possibly Coyote Connector? It did eventually lead to an OutOfMemory exception ( at least months ago ) But as I continue to watch "top" I have pushed it up to tomcat using 108 megs of memory (and it doesnt go away). As this server only has 128 megs of memory, thats pushing it, and that was in the span of maybe 15 minutes. I didnt actually push it to the outofmemory state this time around, as it is quite obviously the same problem I was getting about 4 month ago when I first switched to the 4.x strain. I was hoping the newer version would have solved that issue ( and darned it, I was almost ready to deploy on production server AGAIN! I don't need the clients ripping me a new umm below orafice again! :) Anyways, using the legacy HTTP1.1 connector I have not been able to reproduce the socketException after multiple people pounding on it for the last 10 minutes. That makes me happy... I also wish I could help you with the tcp/ip, telnet or sniffer thing, but unfortunately I am not that intelligent :) > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 19, 2002 9:50 AM > To: Tomcat Users List > Subject: Re: 4.1.17 Problems - Possibly Coyote Connector? > > > socket closed exception you will have possible for ever..... > > that is problem of tcp/ip and not tomcat....the patch fixes > that the writer > the jsp pages used, isn't clean recylce for the next request..... > > what are you getting from tomcat?..... > > can you try it via telnet/ or with sniffer running in the > background catching > the http conversation.. > > OutOfMemory exception? > > > On Thursday 19 December 2002 15:39, you wrote: > > Ack, whatever was fixed not to cause the blank pages being > served seems to > > still have the underlying problem for me... It also occured > int 4.1.12 > > see error at bottom.... > > > > I'd like to restate that this error continues to occur and > the server will > > eventually run out of memory > > > > I am going to test the old HTTP1.1 connector now, to see if > I still get the > > below exception... > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, December 19, 2002 8:56 AM > > > To: Tomcat Users List > > > Subject: Re: 4.1.17 Problems - Possibly Coyote Connector? > > > > > > > > > This is bug in 4.1.17 which will fixed in Tomcat 4.1.18, > > > > > > i attach the compiled classes that fixe it. > > > > > > update the tomcat-coyote and it should work... > > > > > > On Thursday 19 December 2002 14:33, you wrote: > > > > * Luc Foisy <[EMAIL PROTECTED]> [1214 20:14]: > > > > > > > The actual web application did not seem to have a > problem on > > > > > > > the front side. Everything went on as normal on 4.1.12 > > > > > > > Pages failed to be served correctly on 4.1.17 ( they are > > > > > > > blank ) though logging on with a new session will > serve the > > > > > > > first couple pages then start blanking. > > > > > > > > > > > > This looks like exactly what is happening to me. 4.1.12 > > > > > > works, 4.1.17 gives me the problem. One thing to > note is that my > > > > > > application does not use JSP so must be a catalina or > > > > > > coyote issue. Are > > > > > > > > > you using the stock Coyote/HTTP 1.1 connector or are > > > > > > you using one of > > > > > > > > > the JK connectors? > > > > > > > > > > I am using whatever 4.1.x is set to use by default. Which > > > > > > I am pretty > > > > > > > > sure is the Coyote/HTTP 1.1 connectors. > > > > > > > > This might be a dumb question, but have you tried using the > > > > > > older http/1.1 > > > > > > > connectors to see if the problem goes away? At least then > > > > > > you know it's > > > > > > > Coyote's fault. > > > > 2002-12-19 09:37:32 StandardWrapperValve[jsp]: Servlet.service() for > > servlet jsp threw exception > org.apache.jasper.JasperException: Socket > > closed > > at > > > org.apache.jasper.servlet.JspServletWrapper.service(JspServlet > Wrapper.java: > >248) at > > > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet > .java:295) at > > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at > > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilt > er(Applicatio > >nFilterChain.java:247) at > > > org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli > cationFilterC > >hain.java:193) at > > > org.apache.catalina.core.StandardWrapperValve.invoke(StandardW > rapperValve.j > >ava:260) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:643) at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipel > ine.java:480) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja > va:995) at > > > org.apache.catalina.core.StandardContextValve.invoke(StandardC > ontextValve.j > >ava:191) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:643) at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipel > ine.java:480) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja > va:995) at > > > org.apache.catalina.core.StandardContext.invoke(StandardContex > t.java:2415) > > at > > > org.apache.catalina.core.StandardHostValve.invoke(StandardHost > Valve.java:18 > >0) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:643) at > > > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDi > spatcherValve > >.java:170) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:641) at > > > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport > Valve.java:17 > >2) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:641) at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipel > ine.java:480) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja > va:995) at > > > org.apache.catalina.core.StandardEngineValve.invoke(StandardEn > gineValve.jav > >a:174) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:643) at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipel > ine.java:480) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja > va:995) at > > > org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter. > java:223) at > > > org.apache.coyote.http11.Http11Processor.process(Http11Process > or.java:432) > > at > > > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandle > r.processConn > >ection(Http11Protocol.java:386) at > > > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoi > nt.java:534) > > at > > > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( > ThreadPool.ja > >va:530) at java.lang.Thread.run(Thread.java:536) > > ----- Root Cause ----- > > java.net.SocketException: Socket closed > > at java.net.SocketOutputStream.socketWrite0(Native Method) > > at > > > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at > > java.net.SocketOutputStream.write(SocketOutputStream.java:126) at > > > org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutp > utBuffer.doWr > >ite(InternalOutputBuffer.java:668) at > > > org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(C > hunkedOutputF > >ilter.java:166) at > > > org.apache.coyote.http11.InternalOutputBuffer.doWrite(Internal > OutputBuffer. > >java:523) at org.apache.coyote.Response.doWrite(Response.java:524) > > at > > > org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBu > ffer.java:384 > >) at > org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.jav > a:360) at > > > org.apache.coyote.tomcat4.OutputBuffer.flush(OutputBuffer.java:345) at > > > org.apache.coyote.tomcat4.CoyoteResponse.flushBuffer(CoyoteRes > ponse.java:55 > >4) at > > > org.apache.coyote.tomcat4.CoyoteResponseFacade.flushBuffer(Coy > oteResponseFa > >cade.java:227) at > > > org.apache.jasper.runtime.JspWriterImpl.flush(JspWriterImpl.ja > va:211) at > > > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntime > Library.java: > >810) at org.apache.jsp.cancel_jsp._jspService(cancel_jsp.java:114) at > > > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at > > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > > > org.apache.jasper.servlet.JspServletWrapper.service(JspServlet > Wrapper.java: > >204) at > > > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet > .java:295) at > > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at > > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilt > er(Applicatio > >nFilterChain.java:247) at > > > org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli > cationFilterC > >hain.java:193) at > > > org.apache.catalina.core.StandardWrapperValve.invoke(StandardW > rapperValve.j > >ava:260) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:643) at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipel > ine.java:480) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja > va:995) at > > > org.apache.catalina.core.StandardContextValve.invoke(StandardC > ontextValve.j > >ava:191) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:643) at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipel > ine.java:480) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja > va:995) at > > > org.apache.catalina.core.StandardContext.invoke(StandardContex > t.java:2415) > > at > > > org.apache.catalina.core.StandardHostValve.invoke(StandardHost > Valve.java:18 > >0) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:643) at > > > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDi > spatcherValve > >.java:170) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:641) at > > > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport > Valve.java:17 > >2) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:641) at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipel > ine.java:480) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja > va:995) at > > > org.apache.catalina.core.StandardEngineValve.invoke(StandardEn > gineValve.jav > >a:174) at > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValv > eContext.invo > >keNext(StandardPipeline.java:643) at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipel > ine.java:480) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.ja > va:995) at > > > org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter. > java:223) at > > > org.apache.coyote.http11.Http11Processor.process(Http11Process > or.java:432) > > at > > > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandle > r.processConn > >ection(Http11Protocol.java:386) at > > > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoi > nt.java:534) > > at > > > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( > ThreadPool.ja > >va:530) at java.lang.Thread.run(Thread.java:536) > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> For additional > > commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
