More update.
Tomcat response does get through to the client! But browser keeps
spinning and then times out. JK bug may be?
Any advise guys? This is a production environment so I have to get this
sorted.
Vlad
-----Original Message-----
From: Ilyschenko, Vlad
Sent: Monday, March 01, 2004 10:45 AM
To: Tomcat Users List
Subject: RE: Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19
Update.
This is what happens when the load on tomcat is high:
all requests are executed but for some of those tomcat is unable to send
the response back (browser stalls and will eventually time out after the
timeout set in httpd.conf has expired). As the load goes down tomcat is
able to send content back with no problems.
What configuration settings can affect this behavior?
Vlad
-----Original Message-----
From: Ilyschenko, Vlad
Sent: Monday, March 01, 2004 9:46 AM
To: Tomcat Users List
Subject: Problem: Apache 2.0.48 + mod_jk 1.2.6 + tomcat 5.0.19
Hi,
I'm running Solaris 9, Apache 2.0.48, mod_jk 1.2.6 and tomcat 5.0.19 and
I'm getting these messages in apache error log:
(128)Network is unreachable: connect to listener
Those aren't too frequent though but seem to present problems:
We have a monitoring tool that uses commons-httpclient to poll tomcat
every so often and that tool seem to be getting this exception:
27 Feb 2004 10:21:06 ERROR local_services_monitor2-wrk2 - I/O failure
reading response body
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.net.SocketInputStream.read(SocketInputStream.java:182)
at java.io.FilterInputStream.read(FilterInputStream.java:66)
at
java.io.PushbackInputStream.read(PushbackInputStream.java:120)
at
org.apache.commons.httpclient.ChunkedInputStream.getChunkSizeFromInputSt
ream(ChunkedInputStream.java:264)
at
org.apache.commons.httpclient.ChunkedInputStream.nextChunk(ChunkedInputS
tream.java:237)
at
org.apache.commons.httpclient.ChunkedInputStream.read(ChunkedInputStream
.java:192)
at java.io.FilterInputStream.read(FilterInputStream.java:111)
at
org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputSt
ream.java:142)
at java.io.FilterInputStream.read(FilterInputStream.java:90)
at
org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputSt
ream.java:161)
at
org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodB
ase.java:717)
at
org.apache.commons.httpclient.HttpMethodBase.getResponseBodyAsString(Htt
pMethodBase.java:764)
at com.informa.jwatch.jobs.HttpMonitor.start(Unknown Source)
at com.informa.jwatch.jobs.HttpXmlMonitor.start(Unknown Source)
at
com.informa.jwatch.BasicJobContext.executeJob(BasicJobContext.java:32)
at
com.informa.jwatch.AbstractJobContext.execute(AbstractJobContext.java:90
)
at
com.informa.jwatch.BatchJobContext.executeJob(BatchJobContext.java:30)
at
com.informa.jwatch.AbstractJobContext.execute(AbstractJobContext.java:90
)
at
com.informa.jwatch.exec.ExecutionGroup$WorkerThread.run(ExecutionGroup.j
ava:176)
The weird thing is that httpclient always receives http headers and
occasionally fails on the content body.
Basically every time I see that exception in the monitoring log it
coincides with "network unreachable" message in apache error log.
Any ideas on this matter would be greatly appreciated!
Thanks,
Vlad
************************************************************************
********
The information contained in this email message may be confidential. If
you are not the intended recipient, any use, interference with,
disclosure or copying of this material is unauthorised and prohibited.
Although this message and any attachments are believed to be free of
viruses, no responsibility is accepted by Informa for any loss or damage
arising in any way from receipt or use thereof. Messages to and from
the company are monitored for operational reasons and in accordance with
lawful business practices.
If you have received this message in error, please notify us by return
and delete the message and any attachments. Further enquiries/returns
can be sent to [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]
