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]
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]
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]
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]
RE: Broken pipe error
I've never specifically worked with Oracle, but one thing I do know generally is that most DBMS's of my aquaintance don't like open connections that remain inactive for a long period of time (and overnight qualifies as a long period of time). One database I use a lot is MySQL. If the connection remains inactive for too long, MySQL will close that connection but remember that it had closed it due to inactivity. When I try to run a query again using that connection that on my end I think is open, the database returns an error because the connection is closed, but it reopens it. Thus, the second time everything works just fine. I would think that you should be able to trap that kind of an error specifically in an SQLException (says he who has never tried it). The error "connection reset by peer" is certainly a clue, but also not definitive since other things can cause that kind of an error too. Out of curiousity, is that error being generated as an SQLException or an IOException? Hope that helps (and also hope I haven't just rehashed something you've already thoroughly examined). -- Rob --On Friday, February 23, 2001 07:43:21 AM -0500 Randy Layman [EMAIL PROTECTED] 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] _ _ _ _ __ _ _ _ _ /\_\_\_\_\/\_\ /\_\_\_\_\_\ /\/_/_/_/_/ /\/_/ \/_/_/_/_/_/ QUIDQUID LATINE DICTUM SIT, /\/_/__\/_/ __/\/_//\/_/ PROFUNDUM VIDITUR /\/_/_/_/_/ /\_\ /\/_//\/_/ /\/_/ \/_/ /\/_/_/\/_//\/_/ (Whatever is said in Latin \/_/ \/_/ \/_/_/_/_/ \/_/ appears profound) Rob Tanner McMinnville, Oregon [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Broken pipe error
This error drove my nuts. I was using Informix. Finally we used a connection pool called DbBroker from www.javaexchange.com. This pool constantly runs a thread that checks connection status and resets or recreates them if the connection is bad. After using this pool, all of our broken pipe erros are gone. And since there is a repair thread running, we never get a bad connection in our jsp pages unless the db server is stopped. The pool checks connection status before dispensing them. Regards Shahed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
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]
RE: Broken pipe error
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]
RE: Broken pipe error
And I have also the same trouble, but it's a JDBC Exception which is thrown by a JSP page connecting to oracle thru a RMI server.. basically, I'v setup an RMI Interface which offers SQL access to a SGBD, and in the implementation of this Interface I use JDBC stuff to execute the SQL statement... A broken pipe exception is then thrown if the user stays inactif a long time... To my mind, its either the socket in the thin oracle drive which is duty... But I'm still searching for a solution... ___ Laurent LAUBIN S2M Ingnieur systme 2, rue des champs - BP 2282 Tl : +33 232 64 33 76 27950 St-Marcel - France Fax : +33 232 21 25 99 http://www.s2m.fr/ ___ -Message d'origine- De : Cato, Christopher [mailto:[EMAIL PROTECTED]] Envoy : jeudi 22 fvrier 2001 14:37 : '[EMAIL PROTECTED]' Objet : RE: 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. I used to have the exact same problem with my TomCat / MySQL application until i added autoreconnect=true to the db connection initiator method in my general db tool class. Since then, the problem ceased. /Christopher Cato - 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
And I have also the same trouble, but it's a JDBC Exception which is thrown by a JSP page connecting to oracle thru a RMI server.. basically, I'v setup an RMI Interface which offers SQL access to a SGBD, and in the implementation of this Interface I use JDBC stuff to execute the SQL statement... A broken pipe exception is then thrown if the user stays inactif a long time... To my mind, its either the socket in the thin oracle drive which is duty... But I'm still searching for a solution... ___ Laurent LAUBIN S2M Ingnieur systme 2, rue des champs - BP 2282 Tl : +33 232 64 33 76 27950 St-Marcel - France Fax : +33 232 21 25 99 http://www.s2m.fr/ ___ Did you try to set the reconnect = true somewhere? I don't know if it's mm.mysql (the MySQL jdbc driver) specific. If it's not - set it. The connection (or rather the timeout of the connection) is managed by the DB, not the driver. The driver connects on init() and disconnects on destroy(). So, if the DB is set to close the connection after say 900 seconds and your servlets are not used for 1000 seconds, the pipe (connection) would be broken. At least that's the behaviour I've seen. If available, take some time to go through the sources for your JDBC driver and see what's actually going on. /Christopher Cato -Message d'origine- De : Cato, Christopher [mailto:[EMAIL PROTECTED]] Envoy : jeudi 22 fvrier 2001 14:37 : '[EMAIL PROTECTED]' Objet : RE: 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. I used to have the exact same problem with my TomCat / MySQL application until i added autoreconnect=true to the db connection initiator method in my general db tool class. Since then, the problem ceased. /Christopher Cato - 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]
