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
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
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
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
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
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
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
