tomcat connectionpooling/broken pipe

2004-02-12 Thread Mohammed Javid - CTD, Chennai.
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

Re: JK2/tomcat 4.1.18 - broken pipe problem

2003-01-03 Thread Jesper Birch
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

RE: JK2/tomcat 4.1.18 - broken pipe problem

2003-01-03 Thread Venkat Reddy Valluri
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

JK2/tomcat 4.1.18 - broken pipe problem

2003-01-02 Thread Jesper Birch
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

JK2/tomcat 4.1.18 - broken pipe problem

2003-01-02 Thread Jesper Birch
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

RE: JK2/tomcat 4.1.18 - broken pipe problem

2003-01-02 Thread Venkat Reddy Valluri
: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

RE: JK2/tomcat 4.1.18 - broken pipe problem

2003-01-02 Thread Jesper Birch
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

Re: JK2/tomcat 4.1.18 - broken pipe problem

2003-01-02 Thread Bill Barker
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

tomcat and broken pipe

2002-06-25 Thread Raquel R.L.
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

SV: tomcat and broken pipe

2002-06-25 Thread hermod . opstvedt
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