Sorry, I forgot to mention, that we are using mod_jk 1.2.5 on the Apache side
> -----Ursprüngliche Nachricht----- > Von: Hans Schmid [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 22. April 2004 11:25 > An: Tomcat-Dev > Betreff: java.io.IOException: Read bytes failed in Tomcat 3.3.2 with > Coyote Connectors > > > Hello, > > we recently upgraded our production system from Tomcat 3.3.1 with AJP13 > connectors to > Tomcat 3.3.2 with CoyoteConnectors (packaged with TC332) > > We are running behind Apache 1.3.29 on Solaris 9 64bit, J2SDK > 1.4.2_04 from > Sun. > > Monitoring the tomcat.log showed the following Exception which seems to be > CoyoteConnector related. > > java.io.IOException: Read bytes failed -1 > at > org.apache.coyote.tomcat3.Tomcat3Request.readBytes(Tomcat3Request. > java:150) > at > org.apache.coyote.tomcat3.Tomcat3Request.doRead(Tomcat3Request.java:120) > at org.apache.tomcat.core.Request.readBody(Request.java:962) > at > org.apache.tomcat.core.Request.handlePostParameters(Request.java:388) > at > org.apache.tomcat.facade.HttpServletRequestFacade.getParameterName > s(HttpServ > letRequestFacade.java:254) > at > org.apache.struts.util.RequestUtils.populate(RequestUtils.java:743) > at > org.apache.struts.action.ActionServlet.processPopulate(ActionServl > et.java:20 > 61) > at > de.einsurance.gui.framework.ExtendedActionServlet.processPopulate( > ExtendedAc > tionServlet.java:92) > at > org.apache.struts.action.ActionServlet.process(ActionServlet.java:1564) > at > de.einsurance.gui.framework.ExtendedActionServlet.process(Extended > ActionServ > let.java:64) > at > org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510) > at javax.servlet.http.HttpServlet.service(HttpServlet.java) > at javax.servlet.http.HttpServlet.service(HttpServlet.java) > at > org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java:534) > at org.apache.tomcat.core.Handler.invoke(Handler.java:280) > at org.apache.tomcat.core.Handler.service(Handler.java:193) > at > org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:445) > at > org.apache.tomcat.core.ContextManager.internalService(ContextManag > er.java:87 > 4) > at > org.apache.tomcat.core.ContextManager.service(ContextManager.java:790) > at > org.apache.coyote.tomcat3.Tomcat3Adapter.service(Tomcat3Adapter.java:64) > at > org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:296) > at > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:372) > at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:691) > at > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket > .java:625) > at > org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:804) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Thre > adPool.jav > a:644) > at java.lang.Thread.run(Thread.java:534) > > > This looks to me like a Coyote problem. Any Ideas? > What can I do to debug this further (It happen > > Should I file a Bugzilla Entry? > > > (we have 3+ years Experience with the Tomcat 3.3 series and > AJP13Connectors) > > > > Hans Schmid > > einsurance Agency AG > Information Technology > Bayerstrasse 33 > 80335 München > > Tel: +49-89-55292-860 > Fax: +49-89-55292-855 > > > --------------------------------------------------------------------- > 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]
