Dear users.
during the development of my component sometimes I am receiving following error:
HANDLER THREAD PROBLEM: java.io.IOException: Stream broken
java.io.IOException: Stream broken
at
org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp12ConnectionHandler.java:426
5.5, which is two major versions behind
the current Tomcat 7.x version ?
Petr Hracek wrote:
Dear users.
during the development of my component sometimes I am receiving following error:
HANDLER THREAD PROBLEM: java.io.IOException: Stream broken
java.io.IOException: Stream broken
versions are currently 1.2.x but this is not related.
p
Petr Hracek wrote:
Dear users.
during the development of my component sometimes I am receiving
following error:
HANDLER THREAD PROBLEM: java.io.IOException: Stream broken
java.io.IOException: Stream broken
are currently 1.2.x but this is not related.
p
Petr Hracek wrote:
Dear users.
during the development of my component sometimes I am receiving
following error:
HANDLER THREAD PROBLEM: java.io.IOException: Stream broken
java.io.IOException: Stream broken
On 11/07/2011 14:30, Petr Hracek wrote:
It seems that after upgrading to tomcat5.5 all is working.
But some times ps -ef or top shown me that java process is consuming
100% CPU usage
Before that there was used tomcat 3.2.1 version
JRE which was used was 1.4.2.
Right...
So again I'll point
Upgrading to the latest version of tomcat is not so easy on the customer side.
It needs time therefore we have only tomcat 5.5 version. Under SLES10
there is tomcat 5.5 version on the SLES11 there is tomcat 6 version.
Dne 11. července 2011 15:56 Pid p...@pidster.com napsal(a):
On 11/07/2011
Petr Hracek wrote:
Upgrading to the latest version of tomcat is not so easy on the customer side.
It needs time therefore we have only tomcat 5.5 version. Under SLES10
there is tomcat 5.5 version on the SLES11 there is tomcat 6 version.
Allright then, we all have similar customer cases.
And I
From: Petr Hracek [mailto:phrac...@gmail.com]
Subject: Re: HANDLER THREAD PROBLEM: java.io.IOException: Stream broken
Upgrading to the latest version of tomcat is not so easy
on the customer side.
Why not? 6.0.x is configured pretty much identically to 5.5.y.
Under SLES10