This implies you are using mod_jk.  What version of
mod_jk are you using?

There has not been much maintenance on the local mod_jk
provided with Tomcat 3.3.1.  It will be removed in
Tomcat 3.3.2 and replaced by the version which is part
of the jakarta-tomcat-connectors project.  If you haven't
tried it, get the current mod_jk release here:

<http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.2/>

and give it a try.

Unfortunately, I have not had time to keep up with the
changes that have been made to mod_jk since the Tomcat 3.3.1
release.  I'm not sure if "Broke pipe" is that serious an
error or whether may actually be a normal occurrence under
certain circumstances.

However, if a bug in mod_jk or its tomcat connector leaves the
thread servicing the request in a "hung" state when this occurs,
then that could be the source of this problem.  If this was a
problem in older mod_jk's, hopefully it is addressed in the
current release.

Cheers,
Larry

> -----Original Message-----
> From: Liquid [mailto:[EMAIL PROTECTED]] 
> Sent: Tuesday, February 04, 2003 10:16 AM
> To: Tomcat Users List
> Subject: Re: problem using Tomcat 3.3.1
> 
> 
> I use it, but its looks like the same.
> Wahat informations do yuou need from me for help me?
> In my logs is this terrible error.
> 
> java.io.IOException: Broken pipe
>  at java.net.SocketOutputStream.socketWrite(Native Method)
>  at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
>  at org.apache.tomcat.modules.server.Ajp13.send(Ajp13.java:841)
>  at org.apache.tomcat.modules.server.Ajp13.doWrite(Ajp13.java:727)
>  at
> org.apache.tomcat.modules.server.Ajp13Response.doWrite(Ajp13In
> terceptor.java
> :491)
>  at
> org.apache.tomcat.core.OutputBuffer.realWriteBytes(OutputBuffe
> r.java:188)
>  at 
> org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360)
>  at org.apache.tomcat.core.OutputBuffer.flush(OutputBuffer.java:315)
>  at org.apache.tomcat.core.OutputBuffer.close(OutputBuffer.java:305)
>  at
> org.apache.tomcat.facade.ServletWriterFacade.close(ServletWrit
> erFacade.java:
> 117)
>  at GameList.processRequest(GameList.java:963)
>  at GameList.doGet(GameList.java:984)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>  at
> org.apache.tomcat.facade.ServletHandler.doService(ServletHandl
> er.java:574)
>  at org.apache.tomcat.core.Handler.invoke(Handler.java:322)
>  at org.apache.tomcat.core.Handler.service(Handler.java:235)
>  at 
> org.apache.tomcat.facade.ServletHandler.service(ServletHandler
> .java:485)
>  at
> org.apache.tomcat.core.ContextManager.internalService(ContextM
> anager.java:91
> 7)
>  at 
> org.apache.tomcat.core.ContextManager.service(ContextManager.java:833)
>  at
> org.apache.tomcat.modules.server.Ajp13Interceptor.processConne
> ction(Ajp13Int
> erceptor.java:341)
>  at
> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoi
> nt.java:494)
>  at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
> ThreadPool.jav
> a:516)
>  at java.lang.Thread.run(Thread.java:484)
> 
> Thank for your help.
> 
> Liquid
> 
> ----- Original Message -----
> From: "Larry Isaacs" <[EMAIL PROTECTED]>
> To: "Tomcat Users List" <[EMAIL PROTECTED]>
> Sent: Tuesday, February 04, 2003 3:53 PM
> Subject: RE: problem using Tomcat 3.3.1
> 
> 
> There isn't enough information here to offer much help.
> Not knowing what your web application is doing, it
> can't be determined if this is a bug in Tomcat or a
> bug in your web application.
> 
> You are welcome to give Tomcat 3.3.2-dev a quick try
> to see if it behaves differently.  You can find it
> here:
> 
<http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3.x/>


Cheers,
Larry

> -----Original Message-----
> From: Liquid [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 04, 2003 9:43 AM
> To: [EMAIL PROTECTED]
> Subject: problem using Tomcat 3.3.1
>
>
> Hi,
>
> im using Tomcat 3.3.1 on FreeBSD with JDK1.3.1 and my
> aplication go very
> well but afther that take 99% of CPU time and i must restart
> Tomcat. And it
> doing around.
> Can you help me?
>
> Liquid
>
>
> ---------------------------------------------------------------------
> 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]


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

Reply via email to