Additional reasons for broken pipe or connection resets?
Hi. I have a web application that has been working fine for several months, but now it is having some problems. We recently upgraded the OS on the server and version of Java. I'm now getting a large number of connection resets and broken pipe exceptions. For example, today from 10am to 12:30 we had nearly a 100 errors. I've had the network support folks test server network connection. They haven't found any dropped connection problems. I've search the web, this maillist and several newsgroups. In every case, the answer has been that this is caused by the user closing the browser, or selecting reset or just losing the connection. Before our upgrade, we might have gotten 10 error message on a busy day. Now that I am getting so many more errors, I'm concerned that something else could be happening. Is there another reason that might cause a broken pipe or connection reset exception? Thanks, Jeff Duska - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
java.net.SocketException : Broken pipe
Hi, I try to upload a file from an application to another, both using tomcat 4.1.31 and I have the following exception java.net.SocketException : Broken pipe. This happen when I upload large file, I don't reproduce it when I use tomcat 5 or JBoss, can anyone help ? thank you, Nicolas Maujean - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
pooling for java.net.SocketException: Broken pipe connections?
hi, i wonder what tomcats connection pool does when an org.postgresql.util.PSQLException: An IO erro occured while sending to the backend - Exception: java.net.SocketException: Broken pipe exception occurs. will the pool recognize this and get rid of the broken connection? thanx, mischa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SocketException: Broken pipe
Hi there,
I got a problem with a Tomcat 5.5.6 server and Java (jdk and jre
1.5.0_01) on a Debian R3.
On my server, there is a JAVA application which is supposed to connect
to a C++ client appliction through sockets. But it doesn't establish!!
From the logs (catalina.out) I got :
==
[...]
Jan 12, 2005 5:27:58 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener:
attributeAdded('D57CF5B49544DEE007778BB3F78EB407', 'cart',
'[EMAIL PROTECTED]')
processRequest submit = : login
java.net.SocketException: Broken pipe
processRequest submit = : login
processRequest submit = : login
processRequest submit = : refresh
processRequest submit = : refresh
processRequest submit = : refresh
processRequest submit = : refresh
java.net.SocketException: Broken pipe
processRequest submit = : refresh
CheckWebClient execute
checkWebClientConnexion -- 1105547298096
19902
java.net.SocketException: Broken pipe
processRequest submit = : refresh
processRequest submit = : refresh
java.net.SocketException: Broken pipe
processRequest submit = : refresh
[...]
==
I have no enough knowlegde but Tomcat and java to solve this problem. If
some one can help me .
Cheers,
Cédric
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: SocketException: Broken pipe
Hi again
Sorry to insist but it 's quiet important. I running out of ideas to
solve my problem.. :'(
Is there a way to allow/denied access using sockets
Cédric
Hi there,
I got a problem with a Tomcat 5.5.6 server and Java (jdk and jre
1.5.0_01) on a Debian R3.
On my server, there is a JAVA application which is supposed to connect
to a C++ client appliction through sockets. But it doesn't establish!!
From the logs (catalina.out) I got :
==
[...]
Jan 12, 2005 5:27:58 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener:
attributeAdded('D57CF5B49544DEE007778BB3F78EB407', 'cart',
'[EMAIL PROTECTED]')
processRequest submit = : login
java.net.SocketException: Broken pipe
processRequest submit = : login
processRequest submit = : login
processRequest submit = : refresh
processRequest submit = : refresh
processRequest submit = : refresh
processRequest submit = : refresh
java.net.SocketException: Broken pipe
processRequest submit = : refresh
CheckWebClient execute
checkWebClientConnexion -- 1105547298096
19902
java.net.SocketException: Broken pipe
processRequest submit = : refresh
processRequest submit = : refresh
java.net.SocketException: Broken pipe
processRequest submit = : refresh
[...]
==
I have no enough knowlegde but Tomcat and java to solve this problem.
If some one can help me .
Cheers,
Cédric
-
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]
Re: java.net.SocketException: Broken pipe Error
when did u get this error,give me that configure options Rajesh [EMAIL PROTECTED] wrote:Hai in my tomcat logfile am getting the following exception very rarely. Will this will cause any problem in server or in my code ? Aug 14, 2004 11:46:49 AM org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:457) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:654) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:472) at org.apache.coyote.Response.action(Response.java:226) at org.apache.coyote.Response.finish(Response.java:348) at org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:328) at org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse.java:497) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:209) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:324) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:395) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:534) Aug 14, 2004 11:46:49 AM org.apache.jk.server.JkCoyoteHandler action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages!
java.net.SocketException: Broken pipe Error
Hai in my tomcat logfile am getting the following exception very rarely. Will this will cause any problem in server or in my code ? Aug 14, 2004 11:46:49 AM org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:457) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:654) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:472) at org.apache.coyote.Response.action(Response.java:226) at org.apache.coyote.Response.finish(Response.java:348) at org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:328) at org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse.java:497) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:209) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:324) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:395) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:534) Aug 14, 2004 11:46:49 AM org.apache.jk.server.JkCoyoteHandler action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: java.net.SocketException: Broken pipe Error
On Mon, Aug 16, 2004 at 12:34:41PM +0530, Rajesh wrote: : in my tomcat logfile am getting the following exception very rarely. : Will this will cause any problem in server or in my code ? : : : Aug 14, 2004 11:46:49 AM org.apache.jk.server.JkCoyoteHandler action : SEVERE: Error in action code : java.net.SocketException: Broken pipe Please search the archives. I'm getting a sense of deja vu, say, one or two weeks ago. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Broken pipe exception with every request!
Hi, As the error message hints, a common cause for this exception is the client closing the browser while you're generating the page. People do that often when they run into error pages, e.g. as soon as they see the 404 header. I don't know what the rest of your 404.jsp does, but you should try to make it a very simple and quick page (preferably a static one). Yoav Shapira Millennium Research Informatics -Original Message- From: Michael Mehrle [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 27, 2004 4:35 PM To: Tomcat Users List Subject: Broken pipe exception with every request! I got up this morning and noticed that my production server was down. So, I checked tomcat's log and found a whole bunch of these: 2004-07-27 08:09:31 [EMAIL PROTECTED]: Exception Processing ErrorPage[errorCo de=404, location=/404.jsp] ClientAbortException: java.net.SocketException: Broken pipe at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:331) at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:297) at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.jav a:53 7 ) at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteRespon seFa c ade.java:238) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.jav a:30 3 ) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav a:14 7 ) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC onte x t.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav a:11 7 ) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC onte x t.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve .jav a :109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC onte x t.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:7 99) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process Conn e ction(Http11Protocol.ja va:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 77) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja v a:683) at java.lang.Thread.run(Thread.java:534) Tailing the log once I restarted tomcat revealed that this error is being thrown with EVERY REQUEST - no matter what page! Something's very fishy here... BTW - I have the same application running on my staging server and do not get these error messages. Also, the server is pretty slow frankly and I wonder if that's related somehow. Michael - 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]
Re: Broken pipe exception with every request!
Good input, but the site is not being accessed by anyone but me right now and I sure did NOT cancel the page load. So, this is being caused by something else... Michael - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, July 28, 2004 5:50 AM Subject: RE: Broken pipe exception with every request! Hi, As the error message hints, a common cause for this exception is the client closing the browser while you're generating the page. People do that often when they run into error pages, e.g. as soon as they see the 404 header. I don't know what the rest of your 404.jsp does, but you should try to make it a very simple and quick page (preferably a static one). Yoav Shapira Millennium Research Informatics -Original Message- From: Michael Mehrle [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 27, 2004 4:35 PM To: Tomcat Users List Subject: Broken pipe exception with every request! I got up this morning and noticed that my production server was down. So, I checked tomcat's log and found a whole bunch of these: 2004-07-27 08:09:31 [EMAIL PROTECTED]: Exception Processing ErrorPage[errorCo de=404, location=/404.jsp] ClientAbortException: java.net.SocketException: Broken pipe at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:331) at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:297) at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.jav a:53 7 ) at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteRespon seFa c ade.java:238) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.jav a:30 3 ) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav a:14 7 ) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC onte x t.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav a:11 7 ) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC onte x t.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve .jav a :109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC onte x t.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:7 99) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process Conn e ction(Http11Protocol.ja va:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 77) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja v a:683) at java.lang.Thread.run(Thread.java:534) Tailing the log once I restarted tomcat revealed that this error is being thrown with EVERY REQUEST - no matter what page! Something's very fishy here... BTW - I have the same application running on my staging server and do not get these error messages. Also, the server is pretty slow frankly and I wonder if that's related somehow. Michael - 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]
Broken pipe exception with every request!
I got up this morning and noticed that my production server was down. So, I checked tomcat's log and found a whole bunch of these: 2004-07-27 08:09:31 [EMAIL PROTECTED]: Exception Processing ErrorPage[errorCo de=404, location=/404.jsp] ClientAbortException: java.net.SocketException: Broken pipe at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:331) at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:297) at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.java:537 ) at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteResponseFac ade.java:238) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:303 ) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:147 ) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex t.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117 ) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex t.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex t.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.ja va:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:683) at java.lang.Thread.run(Thread.java:534) Tailing the log once I restarted tomcat revealed that this error is being thrown with EVERY REQUEST - no matter what page! Something's very fishy here... BTW - I have the same application running on my staging server and do not get these error messages. Also, the server is pretty slow frankly and I wonder if that's related somehow. Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Broken pipe exception with every request!
Hi, Does anybody know how to hide the JDBCRealm password from server.xml? Thanks Claudio. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
broken pipe - tomcat - jk2
Greetings. Over the past few weeks I've been trying to isolate why some dynamically generated PNG graphics are not visible to the client. The application is deplayed in a multi-tiered implementation. IIS 5.0 webservers running the isapi jk2 ajp13 connectors to tomcat application servers running version 5.0.19.In addition cgi support is enabled and this works fine when not using the ajp13 connectors and going straight to the tomcat application server. [EMAIL PROTECTED] ~]$ telnet special-host 80 Trying 192.168.100.35... Connected to special-host. Escape character is '^]'. GET /cgi-bin/14all.cgi?log=10.99.170.249_13png=daily HTTP/1.0 Accept: */* Accept-Language: en-gb Cookie: JSESSIONID=7E53D518D9D3557831EAA4B531ED88FB User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Host: special-host Connection: Keep-Alive HTTP/1.1 200 OK Server: Microsoft-IIS/5.0 Date: Wed, 07 Apr 2004 16:13:51 GMT Expires: Wed, 07 Apr 2004 16:18:28 GMT Date: Wed, 07 Apr 2004 16:13:28 GMT Content-Type: image/png (png file data --) -- On the application server(s) in the catalina.out this error is visible: Apr 14, 2004 7:32:43 PM org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:489) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:697) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:487) at org.apache.coyote.Response.action(Response.java:226) at org.apache.coyote.Response.finish(Response.java:348) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:344) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:415) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:716) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:650) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:829) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:688) at java.lang.Thread.run(Thread.java:534) Now, I have been successfully sending other types of files, and images, including png back across the pipe -- but for some reason, this doesn't want to work. Is there anything else I can enable or check to help resolve this issue? Is this something that could be resolved by implementing the newest isapi jk2 dll? Thanks in advance. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Broken Pipe (continued) - Thread Dump Results
Hola, I did a thread dump (SIG-QUIT) on both the JRun and Tomcat environments during the refresh button load test and the differences are significant. The differences in internal thread management between any two servers are likely to be significant. Tomcat: Java CPU% exceeds 80%. Site becomes unusable. Thread dump yields approximately 70 threads, just over half are waiting for the DB. Maybe a connection pool problem? I realize this test and its methodology are somewhat arbitrary, but can ANYONE explain what Tomcat (with mod_jk or mod_jk2) is doing with its thread management with excessive broken pipes and why the threads pile up out of control? Can you provide a webapp and test script for us to reproduce your results? PS. I presumed it was bad form to attach documents, but I do have thread dumps available if anyone is willing to take a gander. Not necessarily bad form, but the list won't allow most attachment types. Snip the relevant parts of the tomcat thread dump (the JRun is useless, as the servers are completely different) and post it as a normal message, not an attachment. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Broken Pipe (continued) - Thread Dump Results
Our server does recover (whether JRun or Tomcat), but as Pepijn points out, the thread management during the behaviour is the main concern. I did a thread dump (SIG-QUIT) on both the JRun and Tomcat environments during the refresh button load test and the differences are significant. Between the two environments I observed the following: Tomcat: Java CPU% exceeds 80%. Site becomes unusable. Thread dump yields approximately 70 threads, just over half are waiting for the DB. JRun: Java reaches approximately 42% CPU. The site is usable and improves over time. Thread dump yields only about 18 threads, mostly in Object.wait() state. I realize this test and its methodology are somewhat arbitrary, but can ANYONE explain what Tomcat (with mod_jk or mod_jk2) is doing with its thread management with excessive broken pipes and why the threads pile up out of control? PS. I presumed it was bad form to attach documents, but I do have thread dumps available if anyone is willing to take a gander. -- Chris Boyce - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Broken pipe... PART 2...
In my case, tomcat does not recover. but what I would like to get answered are the questions about the behavior of tomcat in my mail. I think it doesn't matter if it gets crashed or not, it's just the fact that a processors stays processing a job after apache allready dropped it's own thread etc... Pepijn On Fri, 19 Mar 2004, David Rees wrote: Chris Boyce wrote: Just to add my own observations... I can push over our test environment simply by hitting refresh (rapidly) for our front page, which does contain some SQL queries. By just one browser continuously interrupting the connections with refresh, I can watch the Java process in top climb over 80% CPU and the site becomes unresponsive. Can you send Tomcat a QUIT signal so that you can get a stack trace and see what all the Tomcat threads are doing? Does Tomcat eventually recover if you let it sit a while? -Dave - 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]
Broken pipe...
Hello there, When I use apache + mod_jk + tomcat I see something \strange\. When I connect my browser via apache to a servlet, hit the refresh button before I got a response this happens: - the tcp connection between browser and tomcat server is dropped. - apache knows that it's thread can be recycled and stops serving this useless request. - tomcat doesn't stop processing the request to the servlet. - a new processor is started. - the old one exits after a while with a 'Broken pipe' message. (jara.io.IOException) Is there any way to get the java/tomcat thread stopped when apache detects that a certain request is no longer needed ? At this moment, if I just keep refreshing some servlet my machine gets way to slow due to the fact that it has to process a lot of useless requests. As you can understand, suppose a servlet takes 2 seconds to process, the more I hit refresh, the slower the processing of a thread becomes, and the more people get fed up waiting for a response and hitting refresh, and the slower the tomcat server gets After a while, the tomcat doesn't even respond anymore. I found some solution in tuning the min/max processors in server.xml, tuning the acceptCount etc... but I think the main solution lies in the way tomcat handles the 'no longer needed' requests. Maybe another connector between apache and tomcat does tell tomcat it can stop the request ? As far as I know the ajp13(mod_jk) protocol is an asynchronous protocol. Is that correct ? Regards, Pepijn Palmans Managing Director Kangaroot Linux Solutions Grote Steenweg 91 2600 Berchem, Antwerpen Tel: +32 3/286.17.17 Fax: +32 3/281.23.49 Email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Broken pipe... PART 2...
I was literally about to post on the same subject. If anyone knows how Tomcat (and in my case Apache 2.0.48+mod_jk2 on Solaris 8) handles interrupted/broken connections this would be helpful. Just to add my own observations... I can push over our test environment simply by hitting refresh (rapidly) for our front page, which does contain some SQL queries. By just one browser continuously interrupting the connections with refresh, I can watch the Java process in top climb over 80% CPU and the site becomes unresponsive. With the SAME test pointed at JRun 3.0, I cannot push JRun over the edge... Java reaches approximately 40-50% CPU and levels off. What could Tomcat (or at least Tomcat 4.1.30) be doing differently than JRun in handling these adverse threads? Does Tomcat 5 handle this any differently? Thanks On Fri, 2004-03-19 at 08:15, Pepijn Palmans - Kangaroot wrote: Hello there, When I use apache + mod_jk + tomcat I see something \strange\. When I connect my browser via apache to a servlet, hit the refresh button before I got a response this happens: - the tcp connection between browser and tomcat server is dropped. - apache knows that it's thread can be recycled and stops serving this useless request. - tomcat doesn't stop processing the request to the servlet. - a new processor is started. - the old one exits after a while with a 'Broken pipe' message. (jara.io.IOException) Is there any way to get the java/tomcat thread stopped when apache detects that a certain request is no longer needed ? At this moment, if I just keep refreshing some servlet my machine gets way to slow due to the fact that it has to process a lot of useless requests. As you can understand, suppose a servlet takes 2 seconds to process, the more I hit refresh, the slower the processing of a thread becomes, and the more people get fed up waiting for a response and hitting refresh, and the slower the tomcat server gets After a while, the tomcat doesn't even respond anymore. I found some solution in tuning the min/max processors in server.xml, tuning the acceptCount etc... but I think the main solution lies in the way tomcat handles the 'no longer needed' requests. Maybe another connector between apache and tomcat does tell tomcat it can stop the request ? As far as I know the ajp13(mod_jk) protocol is an asynchronous protocol. Is that correct ? Regards, Pepijn Palmans Managing Director Kangaroot Linux Solutions Grote Steenweg 91 2600 Berchem, Antwerpen Tel: +32 3/286.17.17 Fax: +32 3/281.23.49 Email: [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]
Re: Broken pipe... PART 2...
Just to add some PART 3... it might be usefull to have the mod_jk connector give a clear message other than 404 to the browser, wouldn't it ? (of course we can setup a custom 404, but it's not the same as a real 404 !) Pepijn On Fri, 19 Mar 2004, Chris Boyce wrote: I was literally about to post on the same subject. If anyone knows how Tomcat (and in my case Apache 2.0.48+mod_jk2 on Solaris 8) handles interrupted/broken connections this would be helpful. Just to add my own observations... I can push over our test environment simply by hitting refresh (rapidly) for our front page, which does contain some SQL queries. By just one browser continuously interrupting the connections with refresh, I can watch the Java process in top climb over 80% CPU and the site becomes unresponsive. With the SAME test pointed at JRun 3.0, I cannot push JRun over the edge... Java reaches approximately 40-50% CPU and levels off. What could Tomcat (or at least Tomcat 4.1.30) be doing differently than JRun in handling these adverse threads? Does Tomcat 5 handle this any differently? Thanks On Fri, 2004-03-19 at 08:15, Pepijn Palmans - Kangaroot wrote: Hello there, When I use apache + mod_jk + tomcat I see something \strange\. When I connect my browser via apache to a servlet, hit the refresh button before I got a response this happens: - the tcp connection between browser and tomcat server is dropped. - apache knows that it's thread can be recycled and stops serving this useless request. - tomcat doesn't stop processing the request to the servlet. - a new processor is started. - the old one exits after a while with a 'Broken pipe' message. (jara.io.IOException) Is there any way to get the java/tomcat thread stopped when apache detects that a certain request is no longer needed ? At this moment, if I just keep refreshing some servlet my machine gets way to slow due to the fact that it has to process a lot of useless requests. As you can understand, suppose a servlet takes 2 seconds to process, the more I hit refresh, the slower the processing of a thread becomes, and the more people get fed up waiting for a response and hitting refresh, and the slower the tomcat server gets After a while, the tomcat doesn't even respond anymore. I found some solution in tuning the min/max processors in server.xml, tuning the acceptCount etc... but I think the main solution lies in the way tomcat handles the 'no longer needed' requests. Maybe another connector between apache and tomcat does tell tomcat it can stop the request ? As far as I know the ajp13(mod_jk) protocol is an asynchronous protocol. Is that correct ? Regards, Pepijn Palmans Managing Director Kangaroot Linux Solutions Grote Steenweg 91 2600 Berchem, Antwerpen Tel: +32 3/286.17.17 Fax: +32 3/281.23.49 Email: [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]
Re: Broken pipe... PART 4...
I actually don't get 404's... the site just grinds to a halt, and jk_2 spews tonnes of messages like this: Fri Mar 12 15:57:47 2004] [error] ajp13.service() Error forwarding ajp13:localhost:8009 1 0 [Fri Mar 12 15:57:47 2004] [error] mod_jk.handler() Error connecting to tomcat 3 [Fri Mar 12 15:57:48 2004] [error] Error ajp_process_callback - write failed [Fri Mar 12 15:57:48 2004] [error] ajp13.service() ajpGetReply recoverable error 3 [Fri Mar 12 15:57:48 2004] [error] ajp13.service() Error forwarding ajp13:localhost:8009 1 0 [Fri Mar 12 15:57:48 2004] [error] mod_jk.handler() Error connecting to tomcat 3 [Fri Mar 12 15:57:48 2004] [error] Error ajp_process_callback - write failed The messages in catalina.log depend on whether I was recreating the problem in test, or watching it in production. In test, I would get many Broken Pipes, but in production I saw many Closed Sockets. Pepijnm, are you using Windows or a 'nix environment? In Unix, the CPU usage for the JVM goes through the roof. On Fri, 2004-03-19 at 09:52, Pepijn Palmans - Kangaroot wrote: Just to add some PART 3... it might be usefull to have the mod_jk connector give a clear message other than 404 to the browser, wouldn't it ? (of course we can setup a custom 404, but it's not the same as a real 404 !) Pepijn On Fri, 19 Mar 2004, Chris Boyce wrote: I was literally about to post on the same subject. If anyone knows how Tomcat (and in my case Apache 2.0.48+mod_jk2 on Solaris 8) handles interrupted/broken connections this would be helpful. Just to add my own observations... I can push over our test environment simply by hitting refresh (rapidly) for our front page, which does contain some SQL queries. By just one browser continuously interrupting the connections with refresh, I can watch the Java process in top climb over 80% CPU and the site becomes unresponsive. With the SAME test pointed at JRun 3.0, I cannot push JRun over the edge... Java reaches approximately 40-50% CPU and levels off. What could Tomcat (or at least Tomcat 4.1.30) be doing differently than JRun in handling these adverse threads? Does Tomcat 5 handle this any differently? Thanks On Fri, 2004-03-19 at 08:15, Pepijn Palmans - Kangaroot wrote: Hello there, When I use apache + mod_jk + tomcat I see something \strange\. When I connect my browser via apache to a servlet, hit the refresh button before I got a response this happens: - the tcp connection between browser and tomcat server is dropped. - apache knows that it's thread can be recycled and stops serving this useless request. - tomcat doesn't stop processing the request to the servlet. - a new processor is started. - the old one exits after a while with a 'Broken pipe' message. (jara.io.IOException) Is there any way to get the java/tomcat thread stopped when apache detects that a certain request is no longer needed ? At this moment, if I just keep refreshing some servlet my machine gets way to slow due to the fact that it has to process a lot of useless requests. As you can understand, suppose a servlet takes 2 seconds to process, the more I hit refresh, the slower the processing of a thread becomes, and the more people get fed up waiting for a response and hitting refresh, and the slower the tomcat server gets After a while, the tomcat doesn't even respond anymore. I found some solution in tuning the min/max processors in server.xml, tuning the acceptCount etc... but I think the main solution lies in the way tomcat handles the 'no longer needed' requests. Maybe another connector between apache and tomcat does tell tomcat it can stop the request ? As far as I know the ajp13(mod_jk) protocol is an asynchronous protocol. Is that correct ? Regards, Pepijn Palmans Managing Director Kangaroot Linux Solutions Grote Steenweg 91 2600 Berchem, Antwerpen Tel: +32 3/286.17.17 Fax: +32 3/281.23.49 Email: [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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Broken pipe... PART 4...
I'm using Linux I see a lot of 'no processors available' in de catalina_log files. processor usage is indeed eating whole cpu, but machine doesn't die at all. do note that I use mod_jk, not mod_jk2 ! I think there's a whole different way of logging etc. in jk2. also something I don't really like, but can understand is the fact that when I have my maxprocessors on 100, and I use 80 of them on a busy moment, tomcat keeps having 80 processors available in stead of closing them down when they're not needed anymore (cfr. the way apache does with it's threads) Any way to tune that one ? It whould make it easier to see the actual usage of the tomcat on a machine by for instance counting the processes. (as if that is a real solution for monitoring :)) Pepijn On Fri, 19 Mar 2004, Chris Boyce wrote: I actually don't get 404's... the site just grinds to a halt, and jk_2 spews tonnes of messages like this: Fri Mar 12 15:57:47 2004] [error] ajp13.service() Error forwarding ajp13:localhost:8009 1 0 [Fri Mar 12 15:57:47 2004] [error] mod_jk.handler() Error connecting to tomcat 3 [Fri Mar 12 15:57:48 2004] [error] Error ajp_process_callback - write failed [Fri Mar 12 15:57:48 2004] [error] ajp13.service() ajpGetReply recoverable error 3 [Fri Mar 12 15:57:48 2004] [error] ajp13.service() Error forwarding ajp13:localhost:8009 1 0 [Fri Mar 12 15:57:48 2004] [error] mod_jk.handler() Error connecting to tomcat 3 [Fri Mar 12 15:57:48 2004] [error] Error ajp_process_callback - write failed The messages in catalina.log depend on whether I was recreating the problem in test, or watching it in production. In test, I would get many Broken Pipes, but in production I saw many Closed Sockets. Pepijnm, are you using Windows or a 'nix environment? In Unix, the CPU usage for the JVM goes through the roof. On Fri, 2004-03-19 at 09:52, Pepijn Palmans - Kangaroot wrote: Just to add some PART 3... it might be usefull to have the mod_jk connector give a clear message other than 404 to the browser, wouldn't it ? (of course we can setup a custom 404, but it's not the same as a real 404 !) Pepijn On Fri, 19 Mar 2004, Chris Boyce wrote: I was literally about to post on the same subject. If anyone knows how Tomcat (and in my case Apache 2.0.48+mod_jk2 on Solaris 8) handles interrupted/broken connections this would be helpful. Just to add my own observations... I can push over our test environment simply by hitting refresh (rapidly) for our front page, which does contain some SQL queries. By just one browser continuously interrupting the connections with refresh, I can watch the Java process in top climb over 80% CPU and the site becomes unresponsive. With the SAME test pointed at JRun 3.0, I cannot push JRun over the edge... Java reaches approximately 40-50% CPU and levels off. What could Tomcat (or at least Tomcat 4.1.30) be doing differently than JRun in handling these adverse threads? Does Tomcat 5 handle this any differently? Thanks On Fri, 2004-03-19 at 08:15, Pepijn Palmans - Kangaroot wrote: Hello there, When I use apache + mod_jk + tomcat I see something \strange\. When I connect my browser via apache to a servlet, hit the refresh button before I got a response this happens: - the tcp connection between browser and tomcat server is dropped. - apache knows that it's thread can be recycled and stops serving this useless request. - tomcat doesn't stop processing the request to the servlet. - a new processor is started. - the old one exits after a while with a 'Broken pipe' message. (jara.io.IOException) Is there any way to get the java/tomcat thread stopped when apache detects that a certain request is no longer needed ? At this moment, if I just keep refreshing some servlet my machine gets way to slow due to the fact that it has to process a lot of useless requests. As you can understand, suppose a servlet takes 2 seconds to process, the more I hit refresh, the slower the processing of a thread becomes, and the more people get fed up waiting for a response and hitting refresh, and the slower the tomcat server gets After a while, the tomcat doesn't even respond anymore. I found some solution in tuning the min/max processors in server.xml, tuning the acceptCount etc... but I think the main solution lies in the way tomcat handles the 'no longer needed' requests. Maybe another connector between apache and tomcat does tell tomcat it can stop the request ? As far as I know the ajp13(mod_jk) protocol is an asynchronous protocol. Is that correct ? Regards, Pepijn Palmans Managing Director Kangaroot Linux Solutions Grote Steenweg 91 2600 Berchem, Antwerpen Tel: +32 3/286.17.17 Fax: +32 3/281.23.49 Email: [EMAIL
Re: Broken pipe... PART 2...
Chris Boyce wrote: Just to add my own observations... I can push over our test environment simply by hitting refresh (rapidly) for our front page, which does contain some SQL queries. By just one browser continuously interrupting the connections with refresh, I can watch the Java process in top climb over 80% CPU and the site becomes unresponsive. Can you send Tomcat a QUIT signal so that you can get a stack trace and see what all the Tomcat threads are doing? Does Tomcat eventually recover if you let it sit a while? -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat connectionpooling/broken pipe
Hi Is the tomcat connection pooling reliable. We are configuring database properties in server.xml and using the DataSource to lookup the jdbc datasource and get the connection. If in case the database goes down and later it is up, will the tomcat recreate the connections in the pool as the previous connections of pool will be stale. Does tomcat connection pooling has this feature. Though the database is up, we are sometimes noticing the 'broken pipe' error in the log file, when does this error is thrown. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to avoid java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Broken pipe
Hello All, We have tomcat running on the Linux and MSSQL on the win2k . after few queries to database tru servlet we get following exception.We are using JNDI DBCP for the conntionpooling. Error - RemoveAbandonedTimeout: 300 java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Connection reset at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source) at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source) at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source) at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source) at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source) at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source) at com.microsoft.jdbc.base.BaseConnection.getImplConnection(Unknown Source) at com.microsoft.jdbc.base.BaseStatement.setupImplConnection(Unknown Source) at com.microsoft.jdbc.base.BaseStatement.init(Unknown Source) at com.microsoft.jdbc.base.BasePreparedStatement.init(Unknown Source) at com.microsoft.jdbc.base.BaseConnection.prepareStatement(Unknown Source) at com.microsoft.jdbc.base.BaseConnection.prepareStatement(Unknown Source) at org.apache.commons.dbcp.DelegatingConnection.prepareStatement(DelegatingConnection.java:216) at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.prepareStatement(PoolingDataSource.java:323) at com.apsora.servlet_1.AvailServlet.getAvailableTickets(AvailServlet.java:303) at com.apsora.servlet Till now I have two options : Use autoReconnect =true and use validation query. But not sure which is correct and could not get the exact syntxz to add AutoReconnect=true. Thanks in advance... We are in BIG trouble,. Sincerly rahul __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Broken Pipe and Tomcat 4.1.24 -- Fixed?
Im was getting the same error in 4.1.24 then migrated to 4.1.29 but still getting it -Original Message- From: news.basebeans.net [mailto:[EMAIL PROTECTED] Sent: 03 2004 . 22:23 To: [EMAIL PROTECTED] Subject: Broken Pipe and Tomcat 4.1.24 -- Fixed? I'm using Tomcat 4.1.24 and I'm still getting broken pipe stack traces in my catalina log. This ultimately forces a Out of Memory error. Are we certain that this problem was resolved with 4.1.24? (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4663) Lukas - 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]
Broken Pipe and Tomcat 4.1.24 -- Fixed?
I'm using Tomcat 4.1.24 and I'm still getting broken pipe stack traces in my catalina log. This ultimately forces a Out of Memory error. Are we certain that this problem was resolved with 4.1.24? (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4663) Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Broken pipe exception
Hi I received the following exception! We are using Tomcat 4.1.18, jre1.3.1_09 and explorer 6.0.2 The exception happens always if I'm adding elements to a table and I'm refreshing the data from server. The size of this list doesn't matter because I happens just with short lists: 2003-12-12 15:56:19 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java:384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:338) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.java:110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.java:1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:1745) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:506) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) 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:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530) Does anybody know the reason? at java.lang.Thread.run(Thread.java:479) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Broken pipe exception
Which database are you using? -- De: Markus Brigl[SMTP:[EMAIL PROTECTED] Responder:Tomcat Users List Enviada: sexta-feira, 19 de dezembro de 2003 6:06 Para: [EMAIL PROTECTED] Assunto: Broken pipe exception Hi I received the following exception! We are using Tomcat 4.1.18, jre1.3.1_09 and explorer 6.0.2 The exception happens always if I'm adding elements to a table and I'm refreshing the data from server. The size of this list doesn't matter because I happens just with short lists: 2003-12-12 15:56:19 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doW rite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutp utFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer .java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java:38 4) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:338) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.java :110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.java: 1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:1745) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.j ava:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:506) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicati onFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilter Chain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve. java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve. java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:1 80) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValv e.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:1 72) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.ja va:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processCon nection(Http11Protocol.java:386) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.j ava:530) Does anybody know
Re: Broken pipe exception
We use Versant 6.0.5 patch 10! Do you think the problem is connected to the database? Thank's for help! Markus Edson Alves Pereira wrote: Which database are you using? -- De: Markus Brigl[SMTP:[EMAIL PROTECTED] Responder: Tomcat Users List Enviada:sexta-feira, 19 de dezembro de 2003 6:06 Para: [EMAIL PROTECTED] Assunto:Broken pipe exception Hi I received the following exception! We are using Tomcat 4.1.18, jre1.3.1_09 and explorer 6.0.2 The exception happens always if I'm adding elements to a table and I'm refreshing the data from server. The size of this list doesn't matter because I happens just with short lists: 2003-12-12 15:56:19 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doW rite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutp utFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer .java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java:38 4) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:338) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.java :110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.java: 1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:1745) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.j ava:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:506) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicati onFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilter Chain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve. java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve. java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:1 80) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValv e.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:1 72) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.ja va:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processCon nection(Http11Protocol.java:386) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534
RE: Broken pipe exception
Here we have Oracle9i and some time ago, we used to have this problem when too much connection were open with Oracle and some were too much network connection open. I don´t know this database, but maybe its a path to solve it. -- De: Markus Brigl[SMTP:[EMAIL PROTECTED] Responder:Tomcat Users List Enviada: sexta-feira, 19 de dezembro de 2003 9:35 Para: Tomcat Users List Assunto: Re: Broken pipe exception We use Versant 6.0.5 patch 10! Do you think the problem is connected to the database? Thank's for help! Markus Edson Alves Pereira wrote: Which database are you using? -- De: Markus Brigl[SMTP:[EMAIL PROTECTED] Responder: Tomcat Users List Enviada:sexta-feira, 19 de dezembro de 2003 6:06 Para: [EMAIL PROTECTED] Assunto:Broken pipe exception Hi I received the following exception! We are using Tomcat 4.1.18, jre1.3.1_09 and explorer 6.0.2 The exception happens always if I'm adding elements to a table and I'm refreshing the data from server. The size of this list doesn't matter because I happens just with short lists: 2003-12-12 15:56:19 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.d oW rite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOu tp utFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuff er .java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java: 38 4) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:338) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.ja va :110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.jav a: 1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:174 5) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet .j ava:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:50 6) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica ti onFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt er Chain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e. java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nv okeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e. java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nv okeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 5) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :1 80) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nv okeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lv e.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nv okeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :1 72) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nv okeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. ja va:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nv okeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80
RE: Broken pipe exception
Howdy, This is not related to your DB (at least, not likely to be related to your DB). It's probably your user closing the browser while the request is still processing. This issue in Coyote was fixed in Tomcat 4.1.24 I believe, so you should try upgrading to tomcat 4.1.29 or 5.0.16 and see what happens. Yoav Shapira Millennium ChemInformatics -Original Message- From: Markus Brigl [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 4:06 AM To: [EMAIL PROTECTED] Subject: Broken pipe exception Hi I received the following exception! We are using Tomcat 4.1.18, jre1.3.1_09 and explorer 6.0.2 The exception happens always if I'm adding elements to a table and I'm refreshing the data from server. The size of this list doesn't matter because I happens just with short lists: 2003-12-12 15:56:19 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer. doWr ite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityO utpu tFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuf fer. java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java :384 ) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:338) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411 ) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.j ava: 110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.ja va:1 996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:17 45) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServle t.ja va:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:5 06) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic atio nFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFil terC hain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVal ve.j ava:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextVal ve.j ava:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:24 15) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav a:18 0) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherV alve .java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav a:17 2) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve .jav a:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:4 32) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process Conn ection(Http11Protocol.java
Re: Broken pipe exception
Hi, the client is an applet and the browser hasn't been closed! Could it be the applet goes in timeout? Because after this error on server side the applet throws a an exception if we refresh the data! could not send requests to server (root exception: java.io.IOException: First header field does not start with HTTP) Shapira, Yoav wrote: Howdy, This is not related to your DB (at least, not likely to be related to your DB). It's probably your user closing the browser while the request is still processing. This issue in Coyote was fixed in Tomcat 4.1.24 I believe, so you should try upgrading to tomcat 4.1.29 or 5.0.16 and see what happens. Yoav Shapira Millennium ChemInformatics -Original Message- From: Markus Brigl [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 4:06 AM To: [EMAIL PROTECTED] Subject: Broken pipe exception Hi I received the following exception! We are using Tomcat 4.1.18, jre1.3.1_09 and explorer 6.0.2 The exception happens always if I'm adding elements to a table and I'm refreshing the data from server. The size of this list doesn't matter because I happens just with short lists: 2003-12-12 15:56:19 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer. doWr ite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityO utpu tFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuf fer. java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java :384 ) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:338) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411 ) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.j ava: 110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.ja va:1 996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:17 45) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServle t.ja va:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:5 06) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic atio nFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFil terC hain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVal ve.j ava:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextVal ve.j ava:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:24 15) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav a:18 0) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherV alve .java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav a:17 2) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve .jav a:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480
RE: Broken pipe exception
Howdy, the client is an applet and the browser hasn't been closed! Could it be the applet goes in timeout? Because after this error on server side the applet throws a an exception if we refresh the data! Yup, that's a good theory. Have you experimented with the connectionTimeout parameters on the Connector component in server.xml? Yoav Shapira could not send requests to server (root exception: java.io.IOException: First header field does not start with HTTP) Shapira, Yoav wrote: Howdy, This is not related to your DB (at least, not likely to be related to your DB). It's probably your user closing the browser while the request is still processing. This issue in Coyote was fixed in Tomcat 4.1.24 I believe, so you should try upgrading to tomcat 4.1.29 or 5.0.16 and see what happens. Yoav Shapira Millennium ChemInformatics -Original Message- From: Markus Brigl [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 4:06 AM To: [EMAIL PROTECTED] Subject: Broken pipe exception Hi I received the following exception! We are using Tomcat 4.1.18, jre1.3.1_09 and explorer 6.0.2 The exception happens always if I'm adding elements to a table and I'm refreshing the data from server. The size of this list doesn't matter because I happens just with short lists: 2003-12-12 15:56:19 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer. doWr ite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityO utpu tFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuf fer. java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java :384 ) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:338) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411 ) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.j ava: 110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.ja va:1 996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:17 45) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServle t.ja va:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:5 06) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic atio nFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFil terC hain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVal ve.j ava:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextVal ve.j ava:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:24 15) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav a:18 0) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherV alve .java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav a:17 2) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve .jav a:174
Re: Broken pipe exception
The applet might be buggy and close the connection before the entire response is received. (Just a theory) -Tim Markus Brigl wrote: Hi, the client is an applet and the browser hasn't been closed! Could it be the applet goes in timeout? Because after this error on server side the applet throws a an exception if we refresh the data! could not send requests to server (root exception: java.io.IOException: First header field does not start with HTTP) Shapira, Yoav wrote: Howdy, This is not related to your DB (at least, not likely to be related to your DB). It's probably your user closing the browser while the request is still processing. This issue in Coyote was fixed in Tomcat 4.1.24 I believe, so you should try upgrading to tomcat 4.1.29 or 5.0.16 and see what happens. Yoav Shapira Millennium ChemInformatics - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Broken pipe exception
Hi, I don't think the connectionTimeout is the problem. I tought more about corrupted connection than a lost connection, because the applet is made by more internal frames. This special frame will be closed after this error, but applet continues to work! Markus Shapira, Yoav wrote: Howdy, the client is an applet and the browser hasn't been closed! Could it be the applet goes in timeout? Because after this error on server side the applet throws a an exception if we refresh the data! Yup, that's a good theory. Have you experimented with the connectionTimeout parameters on the Connector component in server.xml? Yoav Shapira could not send requests to server (root exception: java.io.IOException: First header field does not start with HTTP) Shapira, Yoav wrote: Howdy, This is not related to your DB (at least, not likely to be related to your DB). It's probably your user closing the browser while the request is still processing. This issue in Coyote was fixed in Tomcat 4.1.24 I believe, so you should try upgrading to tomcat 4.1.29 or 5.0.16 and see what happens. Yoav Shapira Millennium ChemInformatics -Original Message- From: Markus Brigl [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 4:06 AM To: [EMAIL PROTECTED] Subject: Broken pipe exception Hi I received the following exception! We are using Tomcat 4.1.18, jre1.3.1_09 and explorer 6.0.2 The exception happens always if I'm adding elements to a table and I'm refreshing the data from server. The size of this list doesn't matter because I happens just with short lists: 2003-12-12 15:56:19 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer. doWr ite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityO utpu tFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuf fer. java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java :384 ) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:338) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411 ) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.j ava: 110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.ja va:1 996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:17 45) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServle t.ja va:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:5 06) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic atio nFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFil terC hain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVal ve.j ava:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextVal ve.j ava:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:24 15) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav a:18 0) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643
RE: Broken pipe exception
Howdy, Then perhaps as someone else suggested, look for a bug in the applet. Yoav Shapira Millennium ChemInformatics -Original Message- From: Markus Brigl [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 11:03 AM To: Tomcat Users List Subject: Re: Broken pipe exception Hi, I don't think the connectionTimeout is the problem. I tought more about corrupted connection than a lost connection, because the applet is made by more internal frames. This special frame will be closed after this error, but applet continues to work! Markus Shapira, Yoav wrote: Howdy, the client is an applet and the browser hasn't been closed! Could it be the applet goes in timeout? Because after this error on server side the applet throws a an exception if we refresh the data! Yup, that's a good theory. Have you experimented with the connectionTimeout parameters on the Connector component in server.xml? Yoav Shapira could not send requests to server (root exception: java.io.IOException: First header field does not start with HTTP) Shapira, Yoav wrote: Howdy, This is not related to your DB (at least, not likely to be related to your DB). It's probably your user closing the browser while the request is still processing. This issue in Coyote was fixed in Tomcat 4.1.24 I believe, so you should try upgrading to tomcat 4.1.29 or 5.0.16 and see what happens. Yoav Shapira Millennium ChemInformatics -Original Message- From: Markus Brigl [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 4:06 AM To: [EMAIL PROTECTED] Subject: Broken pipe exception Hi I received the following exception! We are using Tomcat 4.1.18, jre1.3.1_09 and explorer 6.0.2 The exception happens always if I'm adding elements to a table and I'm refreshing the data from server. The size of this list doesn't matter because I happens just with short lists: 2003-12-12 15:56:19 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer. doWr ite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityO utpu tFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuf fer. java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java :384 ) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:338) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411 ) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.j ava: 110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.ja va:1 996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:17 45) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServle t.ja va:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:5 06) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic atio nFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFil terC hain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVal ve.j ava:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextVal ve.j ava:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:24 15) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav a:18 0) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo keNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherV alve .java:170
broken pipe
hi this is about the common broken pipe problem (when you press the stop button). i get this mainly in my catalina.out but i was able to redirect a lot of it to context based logger(for each aborded request there are often duzends of lines). if i use jk2 there are also errors in error_log of apache and much more errors in catalina.out etc.. is there any simple way to strip this down ? i'm using tomcat-4.1.29 and turbine 2.2 Apache/2.0.48 (Unix) mod_jk2/2.0.2 thx4any help - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
java.net.SocketException: Broken pipe
Im running tomcat 4.1.29 with mod_jk2 under apache and getting constant stack traces in catalina.out like this one: Dec 8, 2003 8:04:49 PM org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:457) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:654) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:435) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:314) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 615) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:666) at java.lang.Thread.run(Thread.java:536) Have anybody ran over this issue and is it fixable? I already red some posting about firewalls closing connections after some period of time and Stop button pressed in browser. But is there any reasonable solution for this, since i cant ignore firewalls and cant make users not press stop? thanks in advance for any hints
Broken Pipe
I received this error twice before my tomcat 4.1.24 server died. Does anyone know what this error is: 2003-12-04 16:37:45 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599) at org.apache.jk.server.JkCoyoteHandler.doWrite(JkCoyoteHandler.java:216) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java: 384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:439) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:359) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.ja va:110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.jav a:1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:174 5) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet .java:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:50 6) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline. java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline. java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 5) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline. java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline. java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline. java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline. java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:604) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 562) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:619) at java.lang.Thread.run(Thread.java:534) Rob Wichterman Systems Analyst Nuventive 3996 Mount Royal Blvd. Allison Park, PA 15101 Tel: 412-487-7424 Fax: 412-487-3355 Email: [EMAIL PROTECTED] Website: file:///C:\Documents%20and%20Settings\dmoriarty\Application%20Data\Micr osoft\Signatures\www.nuventive.com www.nuventive.com
Io exception: Broken pipe
Hi, I have an application running on Linux-Tomcat. Am using connection pool for Oracle data base connectivity. The problem is , when the Tomcat is kept idle for some time it gives Io exception: Broken pipe help me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Io exception: Broken pipe
Please search commons mailing list. You need to implement sort of keep connection alive using commons-dbcp and pool. -Original Message- From: Omkar Joshi [mailto:[EMAIL PROTECTED] Sent: October 15, 2003 11:46 AM To: [EMAIL PROTECTED] Subject: Io exception: Broken pipe Hi, I have an application running on Linux-Tomcat. Am using connection pool for Oracle data base connectivity. The problem is , when the Tomcat is kept idle for some time it gives Io exception: Broken pipe help me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Broken pipe in Servlet.sercice()
Hi, We have an error that occured several times each day. We use a servlet to send serialized data to a java client. It always append when the servlet sent a big list of objects : 2003-09-15 12:35:56 StandardWrapperValve[ApplicationObjectServlet]: Servlet.service() for servlet ApplicationObjectServlet threw exception java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite (SocketOutputStream.java) at java.net.SocketOutputStream.write(byte[],int,int) (SocketOutputStream.java:91) (pc 15) at org.apache.catalina.connector.ResponseBase.flushBuffer (ResponseBase.java:674) (pc 25) We use GZIPOutputStream to send the data. In archives, I found that other people have had the same problem but it came from the user that click the stop button in the browser. It cannot be the case here because it's during communication between client and server in java directly. Does anybody have an idea about the problem? Is there a limitation to the size of data that we can send by a socket? Cécile SAINT-MARTIN Ouest-France Tel. 77.24 mailto:[EMAIL PROTECTED] -- Les informations ou pièces jointes contenues dans ce message sont confidentielles. Seul le destinataire expressément visé peut en prendre connaissance. Toute autre personne qui en divulguera, diffusera ou prendra des copies sera passible de poursuites. La société Ouest-France décline en outre, toute responsabilité de quelque nature que ce soit au titre de ce message s'il a été altéré, déformé ou falsifié. -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Broken pipe in Servlet.sercice()
Howdy, We use a servlet to send serialized data to a java client. It always append Post the relevant servlet code. Is there a limitation to the size of data that we can send by a socket? No. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : Broken pipe in Servlet.sercice()
Code for ApplicationObjectServlet :
private void recupererListe( HttpServletRequest request,
HttpServletResponse response,
String nomObjet)
throws IOException {
try {
List listeDonnee = (List)
UtilsCom.litSurFluxZippe(request.getInputStream());
ServletContext context = getServletContext();
listeDonnee = (List) context.getAttribute(Liste + nomObjet);
ByteCounterOutputStream byteCounterStream =
new
ByteCounterOutputStream(response.getOutputStream());
int start = byteCounterStream.bytesWrittenSoFar();
UtilsCom.ecritSurFluxZippe((Serializable)listeDonnee,
byteCounterStream);
int objectSize = byteCounterStream.bytesWrittenSoFar() - start;
log.debug(Taille de l'objet serialise : + objectSize + octets);
_nbBytesWritten += objectSize;
}
catch (ClassNotFoundException ex) {
if (log.isEnabledFor(Priority.ERROR)) {
log.error(ex.toString());
}
}
}
ByteCounterOutputStream is just a class that inherit from DataOutputStream
and that permits to know the number of bytes written.
Here is the code for UtilsCom :
public static void ecritSurFluxZippe(Serializable objectToSerialize,
OutputStream out)
throws java.io.IOException{
GZIPOutputStream zipStream = new GZIPOutputStream(out);
ObjectOutputStream objectOutput = new ObjectOutputStream(zipStream);
objectOutput.writeObject(objectToSerialize);
objectOutput.flush();
objectOutput.close();
}
Cécile SAINT-MARTIN
Ouest-France
Tel. 77.24
mailto:[EMAIL PROTECTED]
Howdy,
We use a servlet to send serialized data to a java client. It always
append
Post the relevant servlet code.
Is there a limitation to the size of data that we can send
by a socket?
No.
Yoav Shapira
--
Les informations ou pièces jointes contenues dans ce message sont
confidentielles. Seul le destinataire expressément visé peut en prendre
connaissance. Toute autre personne qui en divulguera, diffusera ou prendra
des copies sera passible de poursuites. La société Ouest-France décline en
outre, toute responsabilité de quelque nature que ce soit au titre de ce
message s'il a été altéré, déformé ou falsifié.
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IE 6 causes broken pipe exception
Here's a followup to: Subject: DefaultServlet throws a LOT of broken pipe exceptions on mp3s. --- I found the cause of my java.io.IOException Broken pipe errors. IE 6 is sending two GET requests for each .mp3 file. I haven't tested the behavior on IE 5.x or other plugin-handled mime types. The first GET sets the request header: user-agent = contype and is a Microsoft (ie, non-standard) attempt at data-sniffing intended to get just the header information. Tomcat 4.x starts sending the content data, but IE resets/drops the connection after 30-50k (100-500 ms), generating a Broken pipe exception. IE then sends a second request for the content using: user-agent=Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) which completes. [see Microsoft Knowledge Base Articles: KB 293792, KB 254337, KB 310388. Note: KB 310388 describes a fix for multiple posts in IE 6 SP1 (service pack 1). Tests from an IE 6 SP1 client however still demonstrate the multiple GETs. I'm still trying to determine if the broken pipe GET is the cause of the unreliable caching behaving I'm seeing in IE 6 (symptom: IE 6 clients are downloading about 10x vs. Netscape/Safari clients; few if any 304 responses). --- So, two questions for the karmically kind: 1) Any bright ideas on a workaround for the user-agent: contype GET? At present it's double-banging my server for 100-200k files. Is there a context level mechanism for filtering, ie, blocking, requests based on headers? 2) Is this more properly a development issue? I see workarounds in the 4.1.27 and 5.x source to ignore Broken pipe exceptions and the multiple GET is apparently rooted in kludges from browser 4.x days -- but I got no hits for user-agent contype in a google of the tomcat archives. Cheers, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IE 6 causes broken pipe exception
Hello Chris! CR IE 6 is sending two GET requests for each .mp3 file. I haven't tested the CR behavior on IE 5.x or other plugin-handled mime types. CR The first GET sets the request header: CR user-agent = contype CR and is a Microsoft (ie, non-standard) attempt at data-sniffing intended to CR get just the header information. Tomcat 4.x starts sending the content data, CR but IE resets/drops the connection after 30-50k (100-500 ms), generating a CR Broken pipe exception. CR IE then sends a second request for the content using: CR user-agent=Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) CR which completes. CR [see Microsoft Knowledge Base Articles: KB 293792, KB 254337, KB 310388. CR Note: KB 310388 describes a fix for multiple posts in IE 6 SP1 (service pack CR 1). Tests from an IE 6 SP1 client however still demonstrate the multiple CR GETs. CR I'm still trying to determine if the broken pipe GET is the cause of the CR unreliable caching behaving I'm seeing in IE 6 (symptom: IE 6 clients are CR downloading about 10x vs. Netscape/Safari clients; few if any 304 CR responses). CR --- CR So, two questions for the karmically kind: CR 1) Any bright ideas on a workaround for the user-agent: contype GET? Yes, this can be handled by servicing your mp3 files via your own servlet. I could check for the user-agent: contype and then probably forwar the request or invoke RequestDispatcher. You may wrap the original request in the wrapper provided by the Servlet 2.3 API substituting the method GET with HEAD. (Do I remember it all correctly?) A more stratagic descision would be to build this into the Tomcat. I've entered an enahncement request to Tomcat bug database including your mail there. You may augment this enhancment request at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23294 CR At CR present it's double-banging my server for 100-200k files. Is there a context CR level mechanism for filtering, ie, blocking, requests based on headers? CR 2) Is this more properly a development issue? I see workarounds in the CR 4.1.27 and 5.x source to ignore Broken pipe exceptions This seems perfectly sane, the client may terminate connection for a multitude of reasons. CR and the multiple GET is apparently rooted in kludges from browser CR 4.x days -- Hmm, what did you mean, Chris? Anton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IE 6 causes broken pipe exception
on 9/20/03 11:07 AM, Anton Tagunov wrote: Hello Chris! CR IE 6 is sending two GET requests for each .mp3 file. I haven't tested the CR behavior on IE 5.x or other plugin-handled mime types. [snip] CR So, two questions for the karmically kind: CR 1) Any bright ideas on a workaround for the user-agent: contype GET? Yes, this can be handled by servicing your mp3 files via your own servlet. I could check for the user-agent: contype and then probably forwar the request or invoke RequestDispatcher. You may wrap the original request in the wrapper provided by the Servlet 2.3 API substituting the method GET with HEAD. (Do I remember it all correctly?) Remapping the contype onto a HEAD seems like a good solution. A more stratagic descision would be to build this into the Tomcat. I've entered an enahncement request to Tomcat bug database including your mail there. You may augment this enhancment request at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23294 Thanks. I'll have a look. CR At CR present it's double-banging my server for 100-200k files. Is there a context CR level mechanism for filtering, ie, blocking, requests based on headers? CR 2) Is this more properly a development issue? I see workarounds in the CR 4.1.27 and 5.x source to ignore Broken pipe exceptions This seems perfectly sane, the client may terminate connection for a multitude of reasons. CR and the multiple GET is apparently rooted in kludges from browser CR 4.x days -- Hmm, what did you mean, Chris? The contype GET has its origins in the days when servers had inconsistent support for the HEAD method and continues to pop up under various guises in IE 4, 5 + 6. So the behaviour has been around for a long, long time. I'm wildly speculating that the workarounds to suppress broken pipe exceptions might be, at least in part, motivated by the excess of broken pipes caused by IE's data-sniffing technique. cheers, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DefaultServlet throws a LOT of broken pipe exceptions on mp3s
Hi, My app logs are filled to bursting with stack traces from broken pipes while serving embedded mp3 (~100k) files. The files serve ok (status 200), but the log clutter is hiding everything else. Strange thing is these aren't the biggest files. 400k jpg's, etc., no problem. The broken pipe exception occurs ONLY on the mp3's. Any suggestions/clues? Thanks, Chris Running Tomcat 4.0.4 on an OS X (10.2) setup. -- NB: org.apache.catalina replaced by [*] to avoid wrapping. -- 2003-09-17 10:03:07 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at [*]connector.ResponseBase.flushBuffer(ResponseBase.java:674) at [*]connector.HttpResponseBase.flushBuffer(HttpResponseBase.java:764) at [*]connector.ResponseBase.write(ResponseBase.java:647) at [*]connector.ResponseStream.write(ResponseStream.java:312) at [*]connector.http.HttpResponseStream.write(HttpResponseStream.java:189) at [*]servlets.DefaultServlet.copyRange(DefaultServlet.java:1903) at [*]servlets.DefaultServlet.copy(DefaultServlet.java:1652) at [*]servlets.DefaultServlet.serveResource(DefaultServlet.java:1197) at [*]servlets.DefaultServlet.doGet(DefaultServlet.java:519) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at [*]core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java: 247) at [*]core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at [*]core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at [*]core.StandardPipeline.invokeNext(StandardPipeline.java:566) at [*]core.StandardPipeline.invoke(StandardPipeline.java:472) at [*]core.ContainerBase.invoke(ContainerBase.java:943) at [*]core.StandardContextValve.invoke(StandardContextValve.java:190) at [*]core.StandardPipeline.invokeNext(StandardPipeline.java:566) at [*]authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:475) at [*]core.StandardPipeline.invokeNext(StandardPipeline.java:564) at [*]valves.CertificatesValve.invoke(CertificatesValve.java:246) at [*]core.StandardPipeline.invokeNext(StandardPipeline.java:564) at [*]core.StandardPipeline.invoke(StandardPipeline.java:472) at [*]core.ContainerBase.invoke(ContainerBase.java:943) at [*]core.StandardContext.invoke(StandardContext.java:2347) at [*]core.StandardHostValve.invoke(StandardHostValve.java:180) at [*]core.StandardPipeline.invokeNext(StandardPipeline.java:566) at [*]valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at [*]core.StandardPipeline.invokeNext(StandardPipeline.java:564) at [*]valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at [*]core.StandardPipeline.invokeNext(StandardPipeline.java:564) at [*]valves.AccessLogValve.invoke(AccessLogValve.java:468) at [*]core.StandardPipeline.invokeNext(StandardPipeline.java:564) at [*]core.StandardPipeline.invoke(StandardPipeline.java:472) at [*]core.ContainerBase.invoke(ContainerBase.java:943) at [*]core.StandardEngineValve.invoke(StandardEngineValve.java:174) at [*]core.StandardPipeline.invokeNext(StandardPipeline.java:566) at [*]core.StandardPipeline.invoke(StandardPipeline.java:472) at [*]core.ContainerBase.invoke(ContainerBase.java:943) at [*]connector.http.HttpProcessor.process(HttpProcessor.java:1027) at [*]connector.http.HttpProcessor.run(HttpProcessor.java:1125) at java.lang.Thread.run(Thread.java:491) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DefaultServlet throws a LOT of broken pipe exceptions on mp3s
Broken pipe means the client the aborted the request which is normal for mp3 since users probably stop listening to the song early. -Tim Chris Rolfe wrote: Hi, My app logs are filled to bursting with stack traces from broken pipes while serving embedded mp3 (~100k) files. The files serve ok (status 200), but the log clutter is hiding everything else. Strange thing is these aren't the biggest files. 400k jpg's, etc., no problem. The broken pipe exception occurs ONLY on the mp3's. Any suggestions/clues? Thanks, Chris Running Tomcat 4.0.4 on an OS X (10.2) setup. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DefaultServlet throws a LOT of broken pipe exceptions on mp3s
That's what I thought at first, but this happens 80-90% of the time on the 100k+ files. There are two files on the same page, one 100-200k dialog, and a 10-30k sentence. It seems to me unlikely the users are hitting stop that quickly and that often. These are reasonably fast university connections in a class setting. Could it be another request hitting the server? Mishandling of partial GETs? Related, the catalina Logger doesn't seem to take Filters (or am I missing something?). I'd like to keep this cruft (in the meantime) out of the log. Chris on 9/18/03 3:57 AM, Tim Funk wrote: Broken pipe means the client the aborted the request which is normal for mp3 since users probably stop listening to the song early. -Tim Chris Rolfe wrote: Hi, My app logs are filled to bursting with stack traces from broken pipes while serving embedded mp3 (~100k) files. The files serve ok (status 200), but the log clutter is hiding everything else. Strange thing is these aren't the biggest files. 400k jpg's, etc., no problem. The broken pipe exception occurs ONLY on the mp3's. Any suggestions/clues? Thanks, Chris Running Tomcat 4.0.4 on an OS X (10.2) setup. - 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]
Re: DefaultServlet throws a LOT of broken pipe exceptions on mp3s
I think in 4.1.24 those messages have been eliminated. Do you get the same errors with wget or similar? It could be the player is sending wacky requests. Otherwise - at 4.0.4 - I'm out of ideas. -Tim Chris Rolfe wrote: That's what I thought at first, but this happens 80-90% of the time on the 100k+ files. There are two files on the same page, one 100-200k dialog, and a 10-30k sentence. It seems to me unlikely the users are hitting stop that quickly and that often. These are reasonably fast university connections in a class setting. Could it be another request hitting the server? Mishandling of partial GETs? Related, the catalina Logger doesn't seem to take Filters (or am I missing something?). I'd like to keep this cruft (in the meantime) out of the log. Chris on 9/18/03 3:57 AM, Tim Funk wrote: Broken pipe means the client the aborted the request which is normal for mp3 since users probably stop listening to the song early. -Tim Chris Rolfe wrote: Hi, My app logs are filled to bursting with stack traces from broken pipes while serving embedded mp3 (~100k) files. The files serve ok (status 200), but the log clutter is hiding everything else. Strange thing is these aren't the biggest files. 400k jpg's, etc., no problem. The broken pipe exception occurs ONLY on the mp3's. Any suggestions/clues? Thanks, Chris Running Tomcat 4.0.4 on an OS X (10.2) setup. - 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]
Re: DefaultServlet throws a LOT of broken pipe exceptions on mp3s
Chris Rolfe wrote: That's what I thought at first, but this happens 80-90% of the time on the 100k+ files. There are two files on the same page, one 100-200k dialog, and a 10-30k sentence. It seems to me unlikely the users are hitting stop that quickly and that often. These are reasonably fast university connections in a class setting. Could it be another request hitting the server? Mishandling of partial GETs? Related, the catalina Logger doesn't seem to take Filters (or am I missing something?). I'd like to keep this cruft (in the meantime) out of the log. I had tested the partial GET with stuff like GetRight and WinAMP (and telnet, obviously). I believe the feature works fine. This exception can only occur on a client disconnect, so the only way it could happen is if too many bytes are written (which, I belive, works fine). BTW, if you run a fileserver on Tomcat (unusal, and not the most efficient server for that use, but it works), then I think you should try 5.0.x, such as 5.0.9 or 5.0.12. -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DefaultServlet throws a LOT of broken pipe exceptions on mp3s
Thanks for both responses. I've got a better idea now what to test. Remy's suggestion of extra bytes being written might plausible, espec. as these are Mac OS files. Sometimes the Apple resource fork messes with little server minds. In the near future, I'll also upgrade to 5.x and move audio + photos onto a different box, but that's a few regression tests away yet. I have been using telnet, jmeter and a RequestDumper valve, but I haven't set up a test plan to bang on the mp3s. Might be worth simulating 20 users on a random timer and see what happens. Anyway, thanks for the help. I'll post back any further findings in case someone's interested. Cheers, Chris on 9/18/03 5:10 AM, Tim Funk wrote: I think in 4.1.24 those messages have been eliminated. Do you get the same errors with wget or similar? It could be the player is sending wacky requests. Otherwise - at 4.0.4 - I'm out of ideas. -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
occasional 403 Errors (revised question) -- jk2 broken pipe error
Sorry, it seems I left out most importan information from my e-mail describing the problem. Below my question revised. ** I have an annoying problem with my setup. I searched the archives and net for similar documented cases and I thought I found the solution, but it does not seem to work. Any hints or ideas would be appreciated. The problem: Occasional 403 access errors to a number of random pages (seemingly with Internet Explorer only). *** There is a 403 error in Apache log and a corresponding broken pipe error in catalina.out log. Setup: Apache 2.047 Tomcat 4.1.27 -- full version *** Tomcat JK2 connector compiled from source (not sure how to determine the version) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28) Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode) Red Hat Linux 2.4.20-13.7 Tomcat catalina log fragment: SEVERE: Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:385) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:268) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:604) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:562) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Thr eadPool.java:619) at java.lang.Thread.run(Thread.java:534) Solutions I tried: Add a random string (comment) to the beginning of the page, since reportedly IE does not handle caching properly (someone suggested that). Strangely enough, this is happening on dynamically generated pages. Also, set max memory for tomcat to 256MB, but no change (earlier ran it with standard settings). TIA, Ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
java.io.IOException: Broken pipe
All, I am receiving java.io.IOException: Broken pipe in Catalina_log. Following are more details. 2003-04-04 09:23:08 Ajp13Processor[13041][33] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:83) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:484) 2003-04-04 09:23:08 Ajp13Processor[13041][33] recyling objects ... Any thoughts ? or Comments? Why I am getting this error. Your suggestions will be a great help! Thanks Narsi Kota - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: java.io.IOException: Broken pipe
try the coyote connector, and see if you have any luck filip -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 7:48 AM To: [EMAIL PROTECTED] Subject: java.io.IOException: Broken pipe All, I am receiving java.io.IOException: Broken pipe in Catalina_log. Following are more details. 2003-04-04 09:23:08 Ajp13Processor[13041][33] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:83) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response. java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:484) 2003-04-04 09:23:08 Ajp13Processor[13041][33] recyling objects ... Any thoughts ? or Comments? Why I am getting this error. Your suggestions will be a great help! Thanks Narsi Kota - 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]
RE: java.io.IOException: Broken pipe
Filip, What is the coyote connector and what do I need to add in server.xml? Please advise. Thanks Narsi Kota Reuse Program Office ISS/App Dev. Center Freddie Mac Ph. (703) 918 8158 Filip Hanik [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] t cc: Subject: RE: java.io.IOException: Broken pipe 04/04/2003 10:54 AM Please respond to Tomcat Users List try the coyote connector, and see if you have any luck filip -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 7:48 AM To: [EMAIL PROTECTED] Subject: java.io.IOException: Broken pipe All, I am receiving java.io.IOException: Broken pipe in Catalina_log. Following are more details. 2003-04-04 09:23:08 Ajp13Processor[13041][33] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:83) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response. java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:484) 2003-04-04 09:23:08 Ajp13Processor[13041][33] recyling objects ... Any thoughts ? or Comments? Why I am getting this error. Your suggestions will be a great help! Thanks Narsi Kota - 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]
RE: java.io.IOException: Broken pipe
Howdy, Coyote is the nickname (as well as the class package name) for the newer HTTP 1.1 connector used by tomcat. I believe this connector is available but not the default with tomcat 4.0.6, and is the default connector in tomcat 4.1.x. It is faster, more robust, and more stable than the previous HTTP 1.1 connector. Look in your server.xml at the Connector elements. Read the connector configuration reference in the documentation. Yoav Shapira Millennium ChemInformatics -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 11:10 AM To: Tomcat Users List Subject: RE: java.io.IOException: Broken pipe Filip, What is the coyote connector and what do I need to add in server.xml? Please advise. Thanks Narsi Kota Reuse Program Office ISS/App Dev. Center Freddie Mac Ph. (703) 918 8158 Filip Hanik [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] t cc: Subject: RE: java.io.IOException: Broken pipe 04/04/2003 10:54 AM Please respond to Tomcat Users List try the coyote connector, and see if you have any luck filip -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 7:48 AM To: [EMAIL PROTECTED] Subject: java.io.IOException: Broken pipe All, I am receiving java.io.IOException: Broken pipe in Catalina_log. Following are more details. 2003-04-04 09:23:08 Ajp13Processor[13041][33] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:83) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response. java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:484) 2003-04-04 09:23:08 Ajp13Processor[13041][33] recyling objects ... Any thoughts ? or Comments? Why I am getting this error. Your suggestions will be a great help! Thanks Narsi Kota - 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] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AJP Connector - Broken Pipe Error
Hi, I am using Tomcat 4.0.6. You said AJP Connector has been re-written in Tomcat 4.1.18. So if I upgrade the version, would my problem get resolved?? Regards, ..Raj -- On Sat, 01 Mar 2003 16:05:06 Sven Köhler wrote: 2003-02-28 13:24:35 Ajp13Processor[8009][42] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:96) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:501) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:484) i have those errors too, although they don't occur that often. btw: which tomcat version do you use? it must be 4.0 or something, because the AJP13 connector has been rewritten in Tomcat 4.1.x. i'm using tomcat 4.1.18. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Need a new email address that people can remember Check out the new EudoraMail at http://www.eudoramail.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AJP Connector - Broken Pipe Error
2003-02-28 13:24:35 Ajp13Processor[8009][42] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:96) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:501) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:484) i have those errors too, although they don't occur that often. btw: which tomcat version do you use? it must be 4.0 or something, because the AJP13 connector has been rewritten in Tomcat 4.1.x. i'm using tomcat 4.1.18. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AJP Connector - Broken Pipe Error
Raja Sekhar [EMAIL PROTECTED] wrote: I have configured my apache server to work with Tomcat engine. But I am continuosly seeing this error in the log file. Use the new Coyote connector instead of the old AJP one. -- Tomasz Nowak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AJP Connector - Broken Pipe Error
Hi Sven, Me to, i'm using tomcat 4.1.18. JP i have those errors too, although they don't occur that often. btw: which tomcat version do you use? it must be 4.0 or something, because the AJP13 connector has been rewritten in Tomcat 4.1.x. i'm using tomcat 4.1.18. - 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]
Re: AJP Connector - Broken Pipe Error
Me to, i'm using tomcat 4.1.18. than you're using an old server.xml. it contains the class-name of the old connector, but there's a new one! plz compare your server.xml with the server.xml that came with tomcat (especially the connector-tags) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AJP Connector - Broken Pipe Error
HI, I have configured my apache server to work with Tomcat engine. But I am continuosly seeing this error in the log file. Can some one help me out at the earliest??? Regards, ..Raj 2003-02-28 13:24:35 Ajp13Processor[8009][42] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:96) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:501) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:484) 2003-02-28 13:24:36 Ajp13Processor[8009][183] Stopping background thread 2003-02-28 13:24:41 Ajp13Processor[8009][182] Stopping background thread 2003-02-28 13:24:44 Ajp13Processor[8009][181] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:96) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:501) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:484) Need a new email address that people can remember Check out the new EudoraMail at http://www.eudoramail.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DBCP Broken Pipe Error - 4.1.18
HI, Env = Apache 2.x , Tomcat 4.1.18 , Oracle 9i , DBCP , Solaris 8 I get the following error after my application has been idle for sometime. The error goes away after I reload my app. 2003-02-14 08:24:22 SQLException: java.sql.SQLException: Io exception: Broken pipe java.sql.SQLException: Io exception: Broken pipe at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:333) at oracle.jdbc.driver.OracleStatement.init(OracleStatement.java:389) at oracle.jdbc.driver.OracleStatement.init(OracleStatement.java:413) at oracle.jdbc.driver.OraclePreparedStatement.init(OraclePreparedStatemen t.java:119) at oracle.jdbc.driver.OracleCallableStatement.init(OracleCallableStatemen t.java:77) at oracle.jdbc.driver.OracleCallableStatement.init(OracleCallableStatemen t.java:48) at oracle.jdbc.driver.OracleConnection.privatePrepareCall(OracleConnection. java:1133) at oracle.jdbc.driver.OracleConnection.prepareCall(OracleConnection.java:98 8) at org.apache.commons.dbcp.DelegatingConnection.prepareCall(DelegatingConne ction.java:205) at conxons.LoginBean.process(LoginBean.java:122) at org.apache.jsp.login_jsp._jspService(login_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(JspServletWrapper.ja va: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.ApplicationDispatcher.invoke(ApplicationDispatc her.java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDisp atcher.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispat cher.java:356) at org.apache.jsp.default_jsp._jspService(default_jsp.java:74) 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(JspServletWrapper.ja va: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.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.ja va:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.ja va:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 5) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.ja va:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve.java:170) Something to do with stale connections ? How do I correct this ? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Broken Pipe
Hi im using Tomcat 3.3.1 with JDK 1.3.1 on FreeBSD and i have stderr.log full of this error and proces of Tomcat take 98 - 100% of CPU time. Can you help me? Many thanks for any help. Liquid stderr.log: - 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(Ajp13Interceptor.java:491) at org.apache.tomcat.core.OutputBuffer.realWriteBytes(OutputBuffer.java:188) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:346) at org.apache.tomcat.util.buf.IntermediateOutputStream.write(C2BConverter.java:234) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:184) at org.apache.tomcat.util.buf.WriteConvertor.write(C2BConverter.java:188) at org.apache.tomcat.util.buf.C2BConverter.convert(C2BConverter.java:113) at org.apache.tomcat.core.OutputBuffer.realWriteChars(OutputBuffer.java:336) at org.apache.tomcat.util.buf.CharChunk.flushBuffer(CharChunk.java:388) at org.apache.tomcat.core.OutputBuffer.flush(OutputBuffer.java:314) at org.apache.tomcat.core.OutputBuffer.close(OutputBuffer.java:305) at org.apache.tomcat.facade.ServletWriterFacade.close(ServletWriterFacade.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(ServletHandler.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(ContextManager.java:917) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:833) at org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection(Ajp13Interceptor.java:341) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:494) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:516) at java.lang.Thread.run(Thread.java:484) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JK2/tomcat 4.1.18 - broken pipe problem
Thx, Bill! But how do I get rid of them in my catalina.out log file ?! Should I set file logging in the worker2.properties ?! jk2.properties ?! Something :-) /Jesper Birch The most common reason for this is that the user has hit the stop button in the browser before the page has been fully loaded. The AJP13 protocol (currently) doesn't support out-of-band messages to notify Tomcat of this fact, so mod_jk(2) simply drops the connection to Tomcat instead. Jesper Birch [EMAIL PROTECTED] wrote in message 1041497967.27623.14.camel@wbirch">news:1041497967.27623.14.camel@wbirch... Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: 500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users of my site has any problems when using it. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! I have built JK2 from the 4.1.18 connectors package.. Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK2/tomcat 4.1.18 - broken pipe problem
I thought this could never be a problem(user htiing stop button), as I alreday mailed, I got it solved by relpacing sun jvm with ibm jvm, But I got it on redhat linux, but you are on solaris right, So what I am thinking is to think this problem in different dimension, This is just my suggestion -Original Message- From: Jesper Birch [mailto:[EMAIL PROTECTED]] Sent: Fri 1/3/2003 6:58 AM To: [EMAIL PROTECTED] Cc: Subject:Re: JK2/tomcat 4.1.18 - broken pipe problem Thx, Bill! But how do I get rid of them in my catalina.out log file ?! Should I set file logging in the worker2.properties ?! jk2.properties ?! Something :-) /Jesper Birch The most common reason for this is that the user has hit the stop button in the browser before the page has been fully loaded. The AJP13 protocol (currently) doesn't support out-of-band messages to notify Tomcat of this fact, so mod_jk(2) simply drops the connection to Tomcat instead. Jesper Birch [EMAIL PROTECTED] wrote in message 1041497967.27623.14.camel@wbirch">news:1041497967.27623.14.camel@wbirch... Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: 500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users of my site has any problems when using it. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! I have built JK2 from the 4.1.18 connectors package.. Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] winmail.dat-- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
JK2/tomcat 4.1.18 - broken pipe problem
Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627)at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372)at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java:500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261)at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users of my site has any problems when using it. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! I have built JK2 from the 4.1.18 connectors package.. Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
JK2/tomcat 4.1.18 - broken pipe problem
Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627)at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372)at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java:500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261)at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users on my site has any problems when it appears. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! Or it should be in that way ?! :-) Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK2/tomcat 4.1.18 - broken pipe problem
Even I too got the same problem with configuraion of apache 2.0.40, tomcat 4.0.4 and j2sdk1.4.1(sun jvm) on redhat 7.3 but when I replaced sun jvm with ibm jvm, surprisingly I didn't get this problem, I am not sure here but what I thought is sun jvm can't support green threads on redhat linux but supports only native threads where as ibm jvm can support green threads on linux machines Thks, -Venkat -Original Message- From: Jesper Birch [mailto:[EMAIL PROTECTED]] Sent: Thu 1/2/2003 6:01 AM To: [EMAIL PROTECTED] Cc: Subject:JK2/tomcat 4.1.18 - broken pipe problem Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627)at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372)at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java:500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261)at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users on my site has any problems when it appears. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! Or it should be in that way ?! :-) Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] winmail.dat-- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK2/tomcat 4.1.18 - broken pipe problem
Hi Thx for the suggestion... I forgot to write that I have the problem on Solaris 7... /Jesper Birch -Original Message- Even I too got the same problem with configuraion of apache 2.0.40, tomcat 4.0.4 and j2sdk1.4.1(sun jvm) on redhat 7.3 but when I replaced sun jvm with ibm jvm, surprisingly I didn't get this problem, I am not sure here but what I thought is sun jvm can't support green threads on redhat linux but supports only native threads where as ibm jvm can support green threads on linux machines Thks, -Venkat -Original Message- Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627)at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.j ava:500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users on my site has any problems when it appears. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! Or it should be in that way ?! :-) Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JK2/tomcat 4.1.18 - broken pipe problem
The most common reason for this is that the user has hit the stop button in the browser before the page has been fully loaded. The AJP13 protocol (currently) doesn't support out-of-band messages to notify Tomcat of this fact, so mod_jk(2) simply drops the connection to Tomcat instead. Jesper Birch [EMAIL PROTECTED] wrote in message 1041497967.27623.14.camel@wbirch">news:1041497967.27623.14.camel@wbirch... Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627)at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: 500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users of my site has any problems when using it. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! I have built JK2 from the 4.1.18 connectors package.. Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Broken pipe msg from Ajp13Processor
I understand why the http connector would get Broken pipe messages - users hitting stop on their browser. But why does the Ajp13Processor produce Broken pipe messages? I'm getting a lot of this in my logs: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:1 96) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:536) I thought that mod_jk held open a single connection to the Ajp13 connector and recycled it? Does it break the Ajp13 connection when the user breaks the http connection? Should I be worried? I'm seeing what feels an awful lot like a thread leak, and I'm wondering if this could be related. I'm running Tomcat 4.0.4 with mod_jk. Thanks in advance, Jeff Schnitzer [EMAIL PROTECTED] The Sims Online -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Broken pipe msg from Ajp13Processor
The number of ajp13 threads in the pool are configurable in the server.xml. A broken pipe is usually caused by someone clicking on a link and then when nothing happens clicking on a different link. So the first click is probably to a slow page (maybe due to a long db query etc). Tomcat will complete rendering the page and then try and write out to the socket, but th socket no longer exists resulting in a Broken pipe. Find out which page is causing this problem and fix it. I have not been able to reproduce this by hitting stop on the browser. Hope that made sense. Subir -Original Message- From: Schnitzer, Jeff [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 27, 2002 4:16 PM To: [EMAIL PROTECTED] Subject: Broken pipe msg from Ajp13Processor I understand why the http connector would get Broken pipe messages - users hitting stop on their browser. But why does the Ajp13Processor produce Broken pipe messages? I'm getting a lot of this in my logs: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:1 96) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:536) I thought that mod_jk held open a single connection to the Ajp13 connector and recycled it? Does it break the Ajp13 connection when the user breaks the http connection? Should I be worried? I'm seeing what feels an awful lot like a thread leak, and I'm wondering if this could be related. I'm running Tomcat 4.0.4 with mod_jk. Thanks in advance, Jeff Schnitzer [EMAIL PROTECTED] The Sims Online -- 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]
Re: Broken pipe msg from Ajp13Processor
At the moment, mod_jk(12) drops the connection to Tomcat if the client drops the connection (e.g. hits the stop button) before the page is fully sent. I won't bore people with the details of why it works this way, but you can usually ignore it. Schnitzer, Jeff [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... I understand why the http connector would get Broken pipe messages - users hitting stop on their browser. But why does the Ajp13Processor produce Broken pipe messages? I'm getting a lot of this in my logs: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:1 96) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:536) I thought that mod_jk held open a single connection to the Ajp13 connector and recycled it? Does it break the Ajp13 connection when the user breaks the http connection? Should I be worried? I'm seeing what feels an awful lot like a thread leak, and I'm wondering if this could be related. I'm running Tomcat 4.0.4 with mod_jk. Thanks in advance, Jeff Schnitzer [EMAIL PROTECTED] The Sims Online -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Broken Pipe Errors
Hi Thanks for the feedback. I don't think that, in our case, there are any direct connections to Tomcat as it is behind a firewall and only Apache is visible. Also we put no-cache etc. in the headers - so hopefully IE will not decide it hasn't changed. Thanks anyway, Anthony. -Original Message- From: Mike Jackson [SMTP:[EMAIL PROTECTED]] Sent: 23 September 2002 23:34 To: Tomcat Users List Subject: RE: Broken Pipe Errors In my experience those broken pipe errors seem to happen most often when Internet Exploder decided that the page hasn't changed. So they may or may not be a real symtom of your problem. But I only got those when I was directly connecting to tomcat, not when I'm using apache as a front end. Don't know if that'll help, but maybe it will. --mikej -=- mike jackson [EMAIL PROTECTED] -Original Message- From: Anthony Milbourne [mailto:[EMAIL PROTECTED]] Sent: Monday, September 23, 2002 10:11 AM To: 'Tomcat Users List' Subject: Broken Pipe Errors Hi I have an install of Apache 1.3.26 talking over mod_jk (4.0.4) to Tomcat 4.0.4 on Solaris 8. All seems to work fine for a while (a couple of days perhaps) - but after a while I get a lot of broken pipe errors in catalina_out.xxx.txt. I previously thought these were due to a missmatch between the number of tomcat processors (maxProcessors) and the number of Apache clients, but this doesn't seem to be the case. The errors are as below. 2002-09-23 00:19:30 Ajp13Processor[8009][3] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196 ) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) 2002-09-23 00:48:51 Ajp13Processor[8009][11] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196 ) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) Eventually I get the error (lots of times): 2002-09-23 10:02:05 Ajp13Connector[8009] No processor available, rejecting this connection Which is fairly serious as nobody can see the site at this point. At this point direct connections to Tomcat (via its HTTP connector on port 8080) don't get a response either. If anyone has any experience/info regarding this I would love to hear it. Thanks, Anthony. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Broken Pipe Errors
Good luck on the no-cache stuff. Does not work with IE, which has a mind of it's own. IE does not adhere to the standards and the solution is to print something unique in the start of the document. I've had more problems with IE and caching than I care to recount. /Christopher -Original Message- From: Anthony Milbourne [mailto:[EMAIL PROTECTED]] Sent: den 24 september 2002 11:09 To: 'Tomcat Users List' Subject: RE: Broken Pipe Errors Hi Thanks for the feedback. I don't think that, in our case, there are any direct connections to Tomcat as it is behind a firewall and only Apache is visible. Also we put no-cache etc. in the headers - so hopefully IE will not decide it hasn't changed. Thanks anyway, Anthony. -Original Message- From: Mike Jackson [SMTP:[EMAIL PROTECTED]] Sent: 23 September 2002 23:34 To: Tomcat Users List Subject:RE: Broken Pipe Errors In my experience those broken pipe errors seem to happen most often when Internet Exploder decided that the page hasn't changed. So they may or may not be a real symtom of your problem. But I only got those when I was directly connecting to tomcat, not when I'm using apache as a front end. Don't know if that'll help, but maybe it will. --mikej -=- mike jackson [EMAIL PROTECTED] -Original Message- From: Anthony Milbourne [mailto:[EMAIL PROTECTED]] Sent: Monday, September 23, 2002 10:11 AM To: 'Tomcat Users List' Subject: Broken Pipe Errors Hi I have an install of Apache 1.3.26 talking over mod_jk (4.0.4) to Tomcat 4.0.4 on Solaris 8. All seems to work fine for a while (a couple of days perhaps) - but after a while I get a lot of broken pipe errors in catalina_out.xxx.txt. I previously thought these were due to a missmatch between the number of tomcat processors (maxProcessors) and the number of Apache clients, but this doesn't seem to be the case. The errors are as below. 2002-09-23 00:19:30 Ajp13Processor[8009][3] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Respo nse.java:196 ) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) 2002-09-23 00:48:51 Ajp13Processor[8009][11] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Respo nse.java:196 ) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) Eventually I get the error (lots of times): 2002-09-23 10:02:05 Ajp13Connector[8009] No processor available, rejecting this connection Which is fairly serious as nobody can see the site at this point. At this point direct connections to Tomcat (via its HTTP connector on port 8080) don't get a response either. If anyone has any experience/info regarding this I would love to hear it. Thanks, Anthony. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** -- 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]
AW: Broken Pipe Errors
To deal with the no-cache stuff we put in every url that shall not be cached a unique id that is incremented with each request. This way you force even IE not to cache the data. (Unless you use javascript() to navigate in the page history) -Ursprüngliche Nachricht- Von: Cato, Christopher [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 24. September 2002 11:14 An: 'Tomcat Users List' Betreff: RE: Broken Pipe Errors Good luck on the no-cache stuff. Does not work with IE, which has a mind of it's own. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Broken Pipe Errors
Hi I have an install of Apache 1.3.26 talking over mod_jk (4.0.4) to Tomcat 4.0.4 on Solaris 8. All seems to work fine for a while (a couple of days perhaps) - but after a while I get a lot of broken pipe errors in catalina_out.xxx.txt. I previously thought these were due to a missmatch between the number of tomcat processors (maxProcessors) and the number of Apache clients, but this doesn't seem to be the case. The errors are as below. 2002-09-23 00:19:30 Ajp13Processor[8009][3] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) 2002-09-23 00:48:51 Ajp13Processor[8009][11] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) Eventually I get the error (lots of times): 2002-09-23 10:02:05 Ajp13Connector[8009] No processor available, rejecting this connection Which is fairly serious as nobody can see the site at this point. At this point direct connections to Tomcat (via its HTTP connector on port 8080) don't get a response either. If anyone has any experience/info regarding this I would love to hear it. Thanks, Anthony. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Broken Pipe Errors
In my experience those broken pipe errors seem to happen most often when Internet Exploder decided that the page hasn't changed. So they may or may not be a real symtom of your problem. But I only got those when I was directly connecting to tomcat, not when I'm using apache as a front end. Don't know if that'll help, but maybe it will. --mikej -=- mike jackson [EMAIL PROTECTED] -Original Message- From: Anthony Milbourne [mailto:[EMAIL PROTECTED]] Sent: Monday, September 23, 2002 10:11 AM To: 'Tomcat Users List' Subject: Broken Pipe Errors Hi I have an install of Apache 1.3.26 talking over mod_jk (4.0.4) to Tomcat 4.0.4 on Solaris 8. All seems to work fine for a while (a couple of days perhaps) - but after a while I get a lot of broken pipe errors in catalina_out.xxx.txt. I previously thought these were due to a missmatch between the number of tomcat processors (maxProcessors) and the number of Apache clients, but this doesn't seem to be the case. The errors are as below. 2002-09-23 00:19:30 Ajp13Processor[8009][3] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) 2002-09-23 00:48:51 Ajp13Processor[8009][11] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) Eventually I get the error (lots of times): 2002-09-23 10:02:05 Ajp13Connector[8009] No processor available, rejecting this connection Which is fairly serious as nobody can see the site at this point. At this point direct connections to Tomcat (via its HTTP connector on port 8080) don't get a response either. If anyone has any experience/info regarding this I would love to hear it. Thanks, Anthony. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** -- 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]
Re: broken pipe and outof memory error
I've had a similar problem with Novell Portal Services on a Win2k/Apache 2.0.40/Tomcat 4.1.10/JDK 1.4 box... memory usage kept climbing and eventually had to reboot system twice after memory usage got to 181M and tomcat spit back a outofmemory error. Tried adding -Xms64m to catalina.bat to see if this would help. Apache is the one that starts Tomcat... Then basically logged into the program found a page and held the refresh key. 7 minutes and 200 megs of ram in use later, apache took over almost all the processor time. Though it looks like it locked all the threads up for apache on the server in my case. [EMAIL PROTECTED] 09/12/02 12:24AM Hello, Following error occurs when a JSP program accesed by number users, this program access information from database though JDBC. Sometime it works fine but when the no. of users accessing it increases , the tomcat server crash with broken pipe or outofmemory error. We had increased the memory also using -Xms32m -Xmx256m But still we are facing the same problem. Error is as following: 2002-09-09 09:28:21 - /vtr: Broken pipe in R( /vtr + /jsp/checkin.jsp + null) - java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.socketWrite(Compiled Code) at java.net.SocketOutputStream.write(Compiled Code) at org.apache.tomcat.modules.server.Http10.sendHeaders(Compiled Code) at org.apache.tomcat.modules.server.HttpResponse.endHeaders(Compiled Code) at org.apache.tomcat.core.OutputBuffer.realWriteBytes(Compiled Code) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(Compiled Code) at org.apache.tomcat.core.OutputBuffer.flush(Compiled Code) at org.apache.tomcat.core.OutputBuffer.close(Compiled Code) at org.apache.tomcat.core.Response.finish(Compiled Code) at org.apache.tomcat.core.ContextManager.service(Compiled Code) at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Compiled Code) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Compiled Code) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Compiled Code) at java.lang.Thread.run(Thread.java:485) 2002-09-09 09:30:06 - /vtr: Broken pipe in R( /vtr + /appl/Qual/jsp/reports.jsp + null) - java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.socketWrite(Compiled Code) at java.net.SocketOutputStream.write(Compiled Code) at org.apache.tomcat.modules.server.Http10.sendHeaders(Compiled Code) at org.apache.tomcat.modules.server.HttpResponse.endHeaders(Compiled Code) at org.apache.tomcat.core.OutputBuffer.realWriteBytes(Compiled Code) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(Compiled Code) at org.apache.tomcat.core.OutputBuffer.flush(Compiled Code) at org.apache.tomcat.core.OutputBuffer.close(Compiled Code) at org.apache.tomcat.core.Response.finish(Compiled Code) at org.apache.tomcat.core.ContextManager.service(Compiled Code) at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Compiled Code) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Compiled Code) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Compiled Code) at java.lang.Thread.run(Thread.java:485) 2002-09-09 10:33:44 - /vtr: Status code:404 request:R( /vtr + /appl/Qual/qtop.html + null) msg:null 2002-09-09 10:33:44 - /vtr: Status code:404 request:R( /vtr + /appl/Qual/qbot.html + null) msg:null 2002-09-09 10:33:59 - /vtr: Exception in R( /vtr + /appl/TurnOver/edata.jsp + null) - java.lang.OutOfMemoryError Thanks in advance, -Geeta Singh -- 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]
Re: broken pipe and outof memory error
Hi, If your servlets or JSP pages have any problems and you see java.lang.OutOfMemoryError in your log files or in a stack trace generated by the Java Virtual Machine (JVM), then you probably need to increase the JVM's maximum heap size. Solaris 1.2 and 1.3 JVMs have a default maximum heap size of 64 MB (and a default minimum heap size of 1 MB). This is a more reasonable figure, but most enterprise level, server-side Java applications require a much higher setting. What setting you choose should be determined by testing and trial and error. It is highly application and load dependent. A good starter article that gives some pointers on how to estimate optimal heap settings is here, at IBM's Java site: http://www-106.ibm.com/developerworks/library/tip-heap-size.html;. You should not try to catch OutOfMemoryErrors in your application. They are not generally predictable. And when they do happen, there's nothing to be done to recover, because by then the JVM is out of memory and the garbage collector is unable to free any memory for further work. Increase the heap size to max value, also try to allocate same value both for min and max parms(Xms512m -Xmx5128m) this should help decreasing heap problems. Actually BrokenPipe errors indicate a networking problem. Data can be sent across the network using pipes in Java. If the pipe suffers some sort of problem an IO exception will be thrown. This are typically seen when a networking problem exists that is serious. Also, could be the result of a servlet timing out. If a servlet makes a connection to a database and the query it requested exceeds the configured timeout period, the thread will timeout and the socket will be closed. The system will throw this exception when it tries to write out the results of the query and discovers that the socket has been closed. Hope this helps -Raj [EMAIL PROTECTED] 09/12/02 04:30PM I've had a similar problem with Novell Portal Services on a Win2k/Apache 2.0.40/Tomcat 4.1.10/JDK 1.4 box... memory usage kept climbing and eventually had to reboot system twice after memory usage got to 181M and tomcat spit back a outofmemory error. Tried adding -Xms64m to catalina.bat to see if this would help. Apache is the one that starts Tomcat... Then basically logged into the program found a page and held the refresh key. 7 minutes and 200 megs of ram in use later, apache took over almost all the processor time. Though it looks like it locked all the threads up for apache on the server in my case. [EMAIL PROTECTED] 09/12/02 12:24AM Hello, Following error occurs when a JSP program accesed by number users, this program access information from database though JDBC. Sometime it works fine but when the no. of users accessing it increases , the tomcat server crash with broken pipe or outofmemory error. We had increased the memory also using -Xms32m -Xmx256m But still we are facing the same problem. Error is as following: 2002-09-09 09:28:21 - /vtr: Broken pipe in R( /vtr + /jsp/checkin.jsp + null) - java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.socketWrite(Compiled Code) at java.net.SocketOutputStream.write(Compiled Code) at org.apache.tomcat.modules.server.Http10.sendHeaders(Compiled Code) at org.apache.tomcat.modules.server.HttpResponse.endHeaders(Compiled Code) at org.apache.tomcat.core.OutputBuffer.realWriteBytes(Compiled Code) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(Compiled Code) at org.apache.tomcat.core.OutputBuffer.flush(Compiled Code) at org.apache.tomcat.core.OutputBuffer.close(Compiled Code) at org.apache.tomcat.core.Response.finish(Compiled Code) at org.apache.tomcat.core.ContextManager.service(Compiled Code) at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Compiled Code) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Compiled Code) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Compiled Code) at java.lang.Thread.run(Thread.java:485) 2002-09-09 09:30:06 - /vtr: Broken pipe in R( /vtr + /appl/Qual/jsp/reports.jsp + null) - java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.socketWrite(Compiled Code) at java.net.SocketOutputStream.write(Compiled Code) at org.apache.tomcat.modules.server.Http10.sendHeaders(Compiled Code) at org.apache.tomcat.modules.server.HttpResponse.endHeaders(Compiled Code) at org.apache.tomcat.core.OutputBuffer.realWriteBytes(Compiled Code) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(Compiled Code) at org.apache.tomcat.core.OutputBuffer.flush(Compiled Code) at org.apache.tomcat.core.OutputBuffer.close(Compiled Code) at org.apache.tomcat.core.Response.finish(Compiled Code) at org.apache.tomcat.core.ContextManager.service(Compiled Code
Re: broken pipe and outof memory error
On a windows machine where apache is starting tomcat, where would I place the switch? I placed it as part of CATALINA_OPS by entering set CATALINA_OPTS=-Xms256m -Xmx512m near the beginning of the catalina.bat startup file. Not sure if this was where to place it or not though. [EMAIL PROTECTED] 09/12/02 04:27PM Hi, If your servlets or JSP pages have any problems and you see java.lang.OutOfMemoryError in your log files or in a stack trace generated by the Java Virtual Machine (JVM), then you probably need to increase the JVM's maximum heap size. Solaris 1.2 and 1.3 JVMs have a default maximum heap size of 64 MB (and a default minimum heap size of 1 MB). This is a more reasonable figure, but most enterprise level, server-side Java applications require a much higher setting. What setting you choose should be determined by testing and trial and error. It is highly application and load dependent. A good starter article that gives some pointers on how to estimate optimal heap settings is here, at IBM's Java site: http://www-106.ibm.com/developerworks/library/tip-heap-size.html;. You should not try to catch OutOfMemoryErrors in your application. They are not generally predictable. And when they do happen, there's nothing to be done to recover, because by then the JVM is out of memory and the garbage collector is unable to free any memory for further work. Increase the heap size to max value, also try to allocate same value both for min and max parms(Xms512m -Xmx5128m) this should help decreasing heap problems. Actually BrokenPipe errors indicate a networking problem. Data can be sent across the network using pipes in Java. If the pipe suffers some sort of problem an IO exception will be thrown. This are typically seen when a networking problem exists that is serious. Also, could be the result of a servlet timing out. If a servlet makes a connection to a database and the query it requested exceeds the configured timeout period, the thread will timeout and the socket will be closed. The system will throw this exception when it tries to write out the results of the query and discovers that the socket has been closed. Hope this helps -Raj [EMAIL PROTECTED] 09/12/02 04:30PM I've had a similar problem with Novell Portal Services on a Win2k/Apache 2.0.40/Tomcat 4.1.10/JDK 1.4 box... memory usage kept climbing and eventually had to reboot system twice after memory usage got to 181M and tomcat spit back a outofmemory error. Tried adding -Xms64m to catalina.bat to see if this would help. Apache is the one that starts Tomcat... Then basically logged into the program found a page and held the refresh key. 7 minutes and 200 megs of ram in use later, apache took over almost all the processor time. Though it looks like it locked all the threads up for apache on the server in my case. [EMAIL PROTECTED] 09/12/02 12:24AM Hello, Following error occurs when a JSP program accesed by number users, this program access information from database though JDBC. Sometime it works fine but when the no. of users accessing it increases , the tomcat server crash with broken pipe or outofmemory error. We had increased the memory also using -Xms32m -Xmx256m But still we are facing the same problem. Error is as following: 2002-09-09 09:28:21 - /vtr: Broken pipe in R( /vtr + /jsp/checkin.jsp + null) - java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.socketWrite(Compiled Code) at java.net.SocketOutputStream.write(Compiled Code) at org.apache.tomcat.modules.server.Http10.sendHeaders(Compiled Code) at org.apache.tomcat.modules.server.HttpResponse.endHeaders(Compiled Code) at org.apache.tomcat.core.OutputBuffer.realWriteBytes(Compiled Code) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(Compiled Code) at org.apache.tomcat.core.OutputBuffer.flush(Compiled Code) at org.apache.tomcat.core.OutputBuffer.close(Compiled Code) at org.apache.tomcat.core.Response.finish(Compiled Code) at org.apache.tomcat.core.ContextManager.service(Compiled Code) at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Compiled Code) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Compiled Code) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Compiled Code) at java.lang.Thread.run(Thread.java:485) 2002-09-09 09:30:06 - /vtr: Broken pipe in R( /vtr + /appl/Qual/jsp/reports.jsp + null) - java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.socketWrite(Compiled Code) at java.net.SocketOutputStream.write(Compiled Code) at org.apache.tomcat.modules.server.Http10.sendHeaders(Compiled Code) at org.apache.tomcat.modules.server.HttpResponse.endHeaders(Compiled Code) at org.apache.tomcat.core.OutputBuffer.realWriteBytes(Compiled Code
broken pipe and outof memory error
Hello, Following error occurs when a JSP program accesed by number users, this program access information from database though JDBC. Sometime it works fine but when the no. of users accessing it increases , the tomcat server crash with broken pipe or outofmemory error. We had increased the memory also using -Xms32m -Xmx256m But still we are facing the same problem. Error is as following: 2002-09-09 09:28:21 - /vtr: Broken pipe in R( /vtr + /jsp/checkin.jsp + null) - java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.socketWrite(Compiled Code) at java.net.SocketOutputStream.write(Compiled Code) at org.apache.tomcat.modules.server.Http10.sendHeaders(Compiled Code) at org.apache.tomcat.modules.server.HttpResponse.endHeaders(Compiled Code) at org.apache.tomcat.core.OutputBuffer.realWriteBytes(Compiled Code) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(Compiled Code) at org.apache.tomcat.core.OutputBuffer.flush(Compiled Code) at org.apache.tomcat.core.OutputBuffer.close(Compiled Code) at org.apache.tomcat.core.Response.finish(Compiled Code) at org.apache.tomcat.core.ContextManager.service(Compiled Code) at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Compiled Code) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Compiled Code) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Compiled Code) at java.lang.Thread.run(Thread.java:485) 2002-09-09 09:30:06 - /vtr: Broken pipe in R( /vtr + /appl/Qual/jsp/reports.jsp + null) - java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.socketWrite(Compiled Code) at java.net.SocketOutputStream.write(Compiled Code) at org.apache.tomcat.modules.server.Http10.sendHeaders(Compiled Code) at org.apache.tomcat.modules.server.HttpResponse.endHeaders(Compiled Code) at org.apache.tomcat.core.OutputBuffer.realWriteBytes(Compiled Code) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(Compiled Code) at org.apache.tomcat.core.OutputBuffer.flush(Compiled Code) at org.apache.tomcat.core.OutputBuffer.close(Compiled Code) at org.apache.tomcat.core.Response.finish(Compiled Code) at org.apache.tomcat.core.ContextManager.service(Compiled Code) at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Compiled Code) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Compiled Code) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Compiled Code) at java.lang.Thread.run(Thread.java:485) 2002-09-09 10:33:44 - /vtr: Status code:404 request:R( /vtr + /appl/Qual/qtop.html + null) msg:null 2002-09-09 10:33:44 - /vtr: Status code:404 request:R( /vtr + /appl/Qual/qbot.html + null) msg:null 2002-09-09 10:33:59 - /vtr: Exception in R( /vtr + /appl/TurnOver/edata.jsp + null) - java.lang.OutOfMemoryError Thanks in advance, -Geeta Singh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
tomcat and broken pipe
Hello! I have a problem with the connection between tomcat and oracle. When I open a connection to the DB once at the beginning, then save it for later. When I come back in several hours, the DB has dropped the connection, so when I try to use it, I get that message, can anyone help me? I don't know what it happens: java.sql.SQLException: Io exception: Broken pipe at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269) at oracle.jdbc.driver.OracleStatement.init(OracleStatement.java:292) at oracle.jdbc.driver.OracleConnection.createStatement(OracleConnection.java:31 3) at es.terra.mobile.smsinvertia.Servidor.insertaRegistro(Servidor.java:38) at es.terra.mobile.smsinvertia.Cliente2Servlet.service(Cliente2Servlet.java:50) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) 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.ja va:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:2 46) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) 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:5 66) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) Thanks, Raquel -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
SV: tomcat and broken pipe
Hi This means that the database has auto-disconnected the connection. In many DB's this is configurable. Otherwise you have to deal with it programmatically. Never leave a connection open after you have finished work on it. Hermod -Opprinnelig melding- Fra: Raquel R.L. [mailto:[EMAIL PROTECTED]] Sendt: 25. juni 2002 12:26 Til: [EMAIL PROTECTED] Emne: tomcat and broken pipe Hello! I have a problem with the connection between tomcat and oracle. When I open a connection to the DB once at the beginning, then save it for later. When I come back in several hours, the DB has dropped the connection, so when I try to use it, I get that message, can anyone help me? I don't know what it happens: java.sql.SQLException: Io exception: Broken pipe at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269) at oracle.jdbc.driver.OracleStatement.init(OracleStatement.java:292) at oracle.jdbc.driver.OracleConnection.createStatement(OracleConnection.jav a:31 3) at es.terra.mobile.smsinvertia.Servidor.insertaRegistro(Servidor.java:38) at es.terra.mobile.smsinvertia.Cliente2Servlet.service(Cliente2Servlet.java :50) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tion FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.ja va:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 72) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.ja va:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 66) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.ja va:2 46) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 72) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:234 3) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 66) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve. java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 64) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 64) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 72) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) Thanks, Raquel -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that DnB cannot accept any payment orders or other legally binding correspondence with customers as a part of an email. This email message has been virus checked by the virus programs used in the DnB Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Broken pipe
Hello list, I'm getting the following error messages when I do a quick refresh on a jsp page: On my engine_log I have: 2002-06-18 17:14:19 Ajp13Request[5] Adding cookie JSESSIONID=F869DFDCF1A1E28C9258B3F10FE76E2E.tomcat1 2002-06-18 17:14:19 Ajp13Processor[8009][4] invoking... 2002-06-18 17:14:19 StandardEngine[Test-Engine]: Mapping server name '198.64.133.217' 2002-06-18 17:14:19 StandardEngine[Test-Engine]: Trying a direct match 2002-06-18 17:14:19 Ajp13Processor[8009][4] done invoking, finishing request/response 2002-06-18 17:14:19 Ajp13Processor[8009][4] process: invoke java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:496) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:192) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:435) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:495) at java.lang.Thread.run(Thread.java:479) ... and on catalina out I get: [Ajp13] Error receiving message I'm using a RedHat Linux Server 2.4.18, glibc 2.2.4, jdk1.3.1_03, tomcat 4.0.2, Apache 1.3.24 with mod_jk-eapi.so, SAPDB and Bitmechanic JDBC Connection Pool. I'm stuck... Any help will be greatefully appreciated... [EMAIL PROTECTED]
RE: Broken pipe
Hi, -Original Message- From: Emerson [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 31, 2002 6:40 PM To: Tomcat Users List Subject: RE: Broken pipe Hi Anton Take a look above, i marked the lines that appear my servlet code : Yeap, sorry. I noticed them when the letter had already been sent. So, you should be able to catch it. And you could rollback the transactions made. The only bad thing, AFAIK, you'll get the exception not earlier then you try to send data back to the user (using either Writer or OutputStream). So, you cant stop the transaction in the middle of execution and your server will have to finnish the job nobody has already been interested in. Isn't it unnecessary resource drain that RFC2616 (8.1.4) talks about? Did I misunderstand it? At 09:38 31/1/2002 +0200, you wrote: Hi, -Original Message- From: Emerson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 30, 2002 7:36 PM To: Tomcat Users List Subject: RE: Broken pipe .java:162) from here: at cadServlet.visualizaEstatiticas(cadServlet.java:690) at cadServlet.doGet(cadServlet.java:351) at cadServlet.doPost(cadServlet.java:408) to here I can catch the exception, cadServlet is the name of the servlet at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at Any mention about your own code, right? So, you can't catch it in your servlet or jsp. Its internal for container. IMHO you'll have to hack into TC to get this IOException. I've been trying to ask about this problem, or if its not a problem and I just crazzy :) I really want to get notified of connection closing event. Nobody answered :( Emerson Cargnin TRE-SC Setor de Desenvolvimento Tel: (48) 251-3700 - Ramal 3134 Anton. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Broken pipe
Hi Anton Take a look above, i marked the lines that appear my servlet code : At 09:38 31/1/2002 +0200, you wrote: Hi, -Original Message- From: Emerson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 30, 2002 7:36 PM To: Tomcat Users List Subject: RE: Broken pipe I haven't tried to get that exception, but i supposse it's possible to pick it up. look at my stacktrace : java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:83) at org.apache.tomcat.service.http.HttpResponseAdapter.endHeaders(Http ResponseAd apter.java:124) at org.apache.tomcat.core.BufferedServletOutputStream.sendHeaders(Buf feredServl etOutputStream.java:126) at org.apache.tomcat.core.BufferedServletOutputStream.reallyFlush(Buf feredServl etOutputStream.java:236) at org.apache.tomcat.core.ResponseImpl.finish(ResponseImpl.java:215) at org.apache.tomcat.facade.RequestDispatcherImpl.doForward(RequestDi spatcherIm pl.java:243) at org.apache.tomcat.facade.RequestDispatcherImpl.forward(RequestDisp atcherImpl .java:162) from here: at cadServlet.visualizaEstatiticas(cadServlet.java:690) at cadServlet.doGet(cadServlet.java:351) at cadServlet.doPost(cadServlet.java:408) to here I can catch the exception, cadServlet is the name of the servlet at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405) at org.apache.tomcat.core.Handler.service(Handler.java:287) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManag er.java:806) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:752) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnec tion(HttpC onnectionHandler.java:213) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484) Any mention about your own code, right? So, you can't catch it in your servlet or jsp. Its internal for container. IMHO you'll have to hack into TC to get this IOException. I've been trying to ask about this problem, or if its not a problem and I just crazzy :) I really want to get notified of connection closing event. Nobody answered :( Emerson Cargnin TRE-SC Setor de Desenvolvimento Tel: (48) 251-3700 - Ramal 3134 -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Broken pipe
Hi, -Original Message- From: Emerson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 29, 2002 10:50 PM To: Tomcat Users List Subject: Broken pipe Is there any way of not throwing an exception java.io.IOException: Broken pipe when the user reloads or cancel the request of a page Or its good to get this exception to rollback all the transactions done already??? Is it possible to get that exception? I mean it's thrown to some internal TC classes. I'd really want my application to be aware of reloading or cancel. Any suggestions? Emerson Cargnin TRE-SC Setor de Desenvolvimento Tel: (48) 251-3700 - Ramal 3134 Anton -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Broken pipe
I haven't tried to get that exception, but i supposse it's possible to pick it up. look at my stacktrace : java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:83) at org.apache.tomcat.service.http.HttpResponseAdapter.endHeaders(HttpResponseAd apter.java:124) at org.apache.tomcat.core.BufferedServletOutputStream.sendHeaders(BufferedServl etOutputStream.java:126) at org.apache.tomcat.core.BufferedServletOutputStream.reallyFlush(BufferedServl etOutputStream.java:236) at org.apache.tomcat.core.ResponseImpl.finish(ResponseImpl.java:215) at org.apache.tomcat.facade.RequestDispatcherImpl.doForward(RequestDispatcherIm pl.java:243) at org.apache.tomcat.facade.RequestDispatcherImpl.forward(RequestDispatcherImpl .java:162) at cadServlet.visualizaEstatiticas(cadServlet.java:690) at cadServlet.doGet(cadServlet.java:351) at cadServlet.doPost(cadServlet.java:408) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405) at org.apache.tomcat.core.Handler.service(Handler.java:287) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:806) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:752) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC onnectionHandler.java:213) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484) At 15:49 30/1/2002 +0200, you wrote: Hi, -Original Message- From: Emerson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 29, 2002 10:50 PM To: Tomcat Users List Subject: Broken pipe Is there any way of not throwing an exception java.io.IOException: Broken pipe when the user reloads or cancel the request of a page Or its good to get this exception to rollback all the transactions done already??? Is it possible to get that exception? I mean it's thrown to some internal TC classes. I'd really want my application to be aware of reloading or cancel. Any suggestions? Emerson Cargnin TRE-SC Setor de Desenvolvimento Tel: (48) 251-3700 - Ramal 3134 Anton -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] Emerson Cargnin TRE-SC Setor de Desenvolvimento Tel: (48) 251-3700 - Ramal 3134 -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Broken pipe
Hi, -Original Message- From: Emerson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 30, 2002 7:36 PM To: Tomcat Users List Subject: RE: Broken pipe I haven't tried to get that exception, but i supposse it's possible to pick it up. look at my stacktrace : java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:83) at org.apache.tomcat.service.http.HttpResponseAdapter.endHeaders(Http ResponseAd apter.java:124) at org.apache.tomcat.core.BufferedServletOutputStream.sendHeaders(Buf feredServl etOutputStream.java:126) at org.apache.tomcat.core.BufferedServletOutputStream.reallyFlush(Buf feredServl etOutputStream.java:236) at org.apache.tomcat.core.ResponseImpl.finish(ResponseImpl.java:215) at org.apache.tomcat.facade.RequestDispatcherImpl.doForward(RequestDi spatcherIm pl.java:243) at org.apache.tomcat.facade.RequestDispatcherImpl.forward(RequestDisp atcherImpl .java:162) at cadServlet.visualizaEstatiticas(cadServlet.java:690) at cadServlet.doGet(cadServlet.java:351) at cadServlet.doPost(cadServlet.java:408) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405) at org.apache.tomcat.core.Handler.service(Handler.java:287) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManag er.java:806) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:752) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnec tion(HttpC onnectionHandler.java:213) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484) Any mention about your own code, right? So, you can't catch it in your servlet or jsp. Its internal for container. IMHO you'll have to hack into TC to get this IOException. I've been trying to ask about this problem, or if its not a problem and I just crazzy :) I really want to get notified of connection closing event. Nobody answered :( At 15:49 30/1/2002 +0200, you wrote: Hi, -Original Message- From: Emerson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 29, 2002 10:50 PM To: Tomcat Users List Subject: Broken pipe Is there any way of not throwing an exception java.io.IOException: Broken pipe when the user reloads or cancel the request of a page Or its good to get this exception to rollback all the transactions done already??? Is it possible to get that exception? I mean it's thrown to some internal TC classes. I'd really want my application to be aware of reloading or cancel. Any suggestions? Emerson Cargnin TRE-SC Setor de Desenvolvimento Tel: (48) 251-3700 - Ramal 3134 Anton -- Emerson Cargnin TRE-SC Setor de Desenvolvimento Tel: (48) 251-3700 - Ramal 3134 Anton -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Broken pipe
Is there any way of not throwing an exception java.io.IOException: Broken pipe when the user reloads or cancel the request of a page Or its good to get this exception to rollback all the transactions done already??? Emerson Cargnin TRE-SC Setor de Desenvolvimento Tel: (48) 251-3700 - Ramal 3134 -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Broken pipe message in tomcat.log
Not sure if this is related or not. I'm getting broken pipe: [Wed Oct 17 08:56:01 2001] [error] [client 216.135.0.25] File does not exist: /home/httpd/html/unsub/a href= [Wed Oct 17 09:11:29 2001] [error] server reached MaxClients setting, consider raising the MaxClients setting [Wed Oct 17 09:29:05 2001] [error] (32)Broken pipe: accept: (client socket) [Wed Oct 17 09:29:06 2001] [error] (32)Broken pipe: accept: (client socket) [Wed Oct 17 09:29:14 2001] [error] (32)Broken pipe: accept: (client socket) [Wed Oct 17 10:06:00 2001] [error] (32)Broken pipe: accept: (client socket) [Wed Oct 17 10:24:34 2001] [error] (32)Broken pipe: accept: (client socket) [Wed Oct 17 10:43:02 2001] [error] (32)Broken pipe: accept: (client socket) [Wed Oct 17 10:43:03 2001] [error] (32)Broken pipe: accept: (client socket) but i think that this is a different pipe than yours ? this completely takes tomcat down until I restart. on 10/18/01 2:39 PM, Tony Mueller at [EMAIL PROTECTED] wrote: Hi, I'm using Tomcat 3.2 and I get the message: Context log: path=/rpm Broken pipe /rpm/servlet/rpm.Login Context log: path=/rpm Broken pipe /rpm/servlet/rpm.Login Context log: path=/rpm Broken pipe /rpm/servlet/rpm.Login Context log: path=/rpm Broken pipe /rpm/servlet/rpm.Login in my tomcat.log file when I try to access my login servlet. This only happens occasionally and makes tomcat hang. I've read the archives and none of the proposed solutions seem to apply to my situation since I'm not using any connection broker in this servlet. Also each call to the servlet establishes a connection and then disconnects so my problem is not related to a connection timing out due to any servlet inactivity. In addition I've checked during this hang to see if I'm running out of db connections. I'm not. Also what is interesting, If I wait about 2 minutes the servlet will finally connect and let my application continue on is merry way (much to the annoyance of my users) I'm sure others are having this problem or have had this problem and found a solution. Thanks Tony Mueller
Broken pipe message in tomcat.log
Hi, I'm using Tomcat 3.2 and I get the message: Context log: path=/rpm Broken pipe /rpm/servlet/rpm.Login Context log: path=/rpm Broken pipe /rpm/servlet/rpm.Login Context log: path=/rpm Broken pipe /rpm/servlet/rpm.Login Context log: path=/rpm Broken pipe /rpm/servlet/rpm.Login in my tomcat.log file when I try to access my login servlet. This only happens occasionally and makes tomcat hang. I've read the archives and none of the proposed solutions seem to apply to my situation since I'm not using any connection broker in this servlet. Also each call to the servlet establishes a connection and then disconnects so my problem is not related to a connection timing out due to any servlet inactivity. In addition I've checked during this hang to see if I'm running out of db connections. I'm not. Also what is interesting, If I wait about 2 minutes the servlet will finally connect and let my application continue on is merry way (much to the annoyance of my users) I'm sure others are having this problem or have had this problem and found a solution. Thanks Tony Mueller
RE: getting Broken pipe: Broken pipe on console
Hello All, After I start up my TOMCAT and apache I get on the console the following exception. I get these exceptions quite a bit while the servlets/JSP's are being accessed, but I can not reproduce these exceptions on demand. == In the servlet log I get the following sometimes. 2001-04-10 02:11:55 - path="" :java.io.IOException: Broken pipe 2001-04-10 02:11:55 - path="" :WriteMessageToBrowserjava.lang.IllegalStateException: Writer is already being used for this request === java.net.SocketException: Broken pipe: Broken pipe at java.net.SocketInputStream.socketRead(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:86) at org.apache.tomcat.service.connector.TcpConnector.receiveFully(TcpConnector.j ava:150) at org.apache.tomcat.service.connector.TcpConnector.receive(TcpConnector.java:1 21) at org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection (Ajp13ConnectionHandler.java:146) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498) at java.lang.Thread.run(Thread.java:484) === Any suggestions on debugging or troubleshooting. Thanks Randy Paries
Re: Broken pipe error
For those who are interested in this issue (yet!) I know that this is not a Tomcat problem but I think it's important! We were working with the following network architecture: Servlets -subnet1--Firewall -subnet2---Database with this scenario we get the error. But we change the architecture to: Servlets subnet1--Database And it works! So we figure out that the problem is in the firewall, it releases the connection. Thanks for the answers, Xavier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Broken pipe error
Thanks for the anwser, but: - The servlet is not garbage collected. When I check it in the mornig, after all night of inactivity, the servlet is active. - Yesterday, I included a connection pooling class. Thus, the servlet re-starts the connection.But I get a "connection reset by peer" error, when trying first access. The second access works fine. Any idea? Regards, Xavier Randy Layman wrote: The answer is no - Tomcat knows nothing about your socket connections and therefore can't close them. A couple of things come to mind - first the Oracle drivers might be releasing the connection, check their documentation about this. Also, what is the behavior if your servlet is garbage collected? Could it be that your servlet is being garbage collected and therefore you are somehow half-way closing the connection? Randy -Original Message- From: Xavier Escandell [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 22, 2001 8:01 AM To: [EMAIL PROTECTED] Subject: Broken pipe error Hi: I get "broken pipe error" when trying to re-execute a servlet after several hours of innactivity. Then I must re-start Tomcat to get all running again. The servlet is connected to a database using oracle thin driver, these connection is still active. So my question is: It is possible that the socket between Tomcat and database is being closed by Tomcat? If the answer is yes, how can I configure these timeout. Regards. Xavier Escandell. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Broken pipe error
The protocol seems to be correct. The thin driver is quite old (classes111.zip) but it match up with the database. Could this driver be in charge of closing connexions? Xavier. Randy Layman wrote: This seems really strange. What it sounds like to me it the JDBC connects one and gets a "Connection reset by peer" error. Then the second (anre presumably more) connections are successful. If this is the case I would check that your drivers and database match up (in other words, not using an old dirver with a new database or vice versa - this may not be applicable to the Oracle thin drivers, I don't know) and also check that you are using the correct protocol. It really shounds like a problem for you, your DBA, and Oracle, though. Randy -Original Message- From: Xavier Escandell [mailto:[EMAIL PROTECTED]] Sent: Friday, February 23, 2001 6:34 AM To: [EMAIL PROTECTED] Subject: Re: Broken pipe error Thanks for the anwser, but: - The servlet is not garbage collected. When I check it in the mornig, after all night of inactivity, the servlet is active. - Yesterday, I included a connection pooling class. Thus, the servlet re-starts the connection.But I get a "connection reset by peer" error, when trying first access. The second access works fine. Any idea? Regards, Xavier Randy Layman wrote: The answer is no - Tomcat knows nothing about your socket connections and therefore can't close them. A couple of things come to mind - first the Oracle drivers might be releasing the connection, check their documentation about this. Also, what is the behavior if your servlet is garbage collected? Could it be that your servlet is being garbage collected and therefore you are somehow half-way closing the connection? Randy -Original Message- From: Xavier Escandell [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 22, 2001 8:01 AM To: [EMAIL PROTECTED] Subject: Broken pipe error Hi: I get "broken pipe error" when trying to re-execute a servlet after several hours of innactivity. Then I must re-start Tomcat to get all running again. The servlet is connected to a database using oracle thin driver, these connection is still active. So my question is: It is possible that the socket between Tomcat and database is being closed by Tomcat? If the answer is yes, how can I configure these timeout. Regards. Xavier Escandell. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] -- Xavier Escandell Ballester Consultor Junior Java Center http://www.javacenter.org Fundaci IBIT http://www.ibit.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
