ar...@bca-group.com wrote:
So I assume adding connectionTimeout attribute to the connector config
could help mitigate this?
Can you be more specific ? which connector's attribute ? the one in the Tomcat
<Connector>, or a setting in mod_jk's workers.properties ?
But anyway, I think not.
There is not really much you can do to make the warning disappear (but note that it is
just a warning, not an error).
You can treat the symptom, by changing the log level in Tomcat to "error"
instead of warning.
Or you can try to find the real cause, which is always better in my opinion.
If the issue is really the one I am describing below, then the question is : why does the
client go away before the whole response can be sent ?
- is there a network problem ?
- or is the application so slow to respond that the user gets impatient and clicks
somewhere else ?
- is there some intermediate agent which closes the connection too quickly ?
- is the application so that at some point some javascript function in the browser window
does a windows.close() before the whole response has been received ?
- is the client a robot that just requests a URL to check it's there, and then immediately
goes away as soon as it gets some answer ?
Maybe the apache logs can help you decide.
André Warnier <a...@ice-sa.com>
24/03/2011 15:15
Please respond to
"Tomcat Users List" <users@tomcat.apache.org>
To
Tomcat Users List <users@tomcat.apache.org>
cc
Subject
Re: Tomcat + apache + mod_jk
Hi.
The schema is :
a) request :
browser -(1)-> (apache + mod_jk) --(2)--> tomcat + app.
b) response :
browser <-(1)-- (apache + mod_jk) <--(2)-- tomcat + app.
So let's say that the browser sends the request, over connection (1), to
apache.
apache creates connection (2) to tomcat, sends the request, and waits for
the response.
tomcat starts sending the response, which apache reads on connection (2),
and starts
forwarding it to the browser over connection (1).
But, for some reason, connection (1) closes (the user closes the browser
or the window, or
whatever). Apache would sense that, since it cannot write anymore to
connection (1).
And it would (probably) close connection (2) then.
So tomcat, when it tries to send the next response part back to apache,
would find a
closed connection (2), and complain.
I don't know if the message below is exactly that case, but maybe it
explains why other
people told you that it could be a network problem. It is not a problem
directly of
connection (2), but on connection (1), just reflected by apache to
connection (2).
ar...@bca-group.com wrote:
For the first time we have received this error (many times). Looks to me
like tomcat cannot talk to apache to me. Can anyone shed any light on
this?
Windows Server 2003
Tomcat: 6.0.16
Apache: 2.2
JDK: 1.6.0_23
Tomcat and Apache on same box so I don't see how it can be a network
issue as some forums are suggesting.
Thanks
24-Mar-2011 13:25:02 org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Software caused connection abort: socket write
error
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:531)
at
org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
at org.apache.jk.core.MsgContext.action(MsgContext.java:304)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.coyote.Response.finish(Response.java:305)
at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:195)
at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
at java.lang.Thread.run(Thread.java:662)
24-Mar-2011 13:25:02 org.apache.jk.common.ChannelSocket
processConnection
WARNING: processCallbacks status 2
This email and any attachments to it may contain confidential
information intended
for the addressee only. If you are not the intended addressee, you are
strictly
prohibited from disclosing, copying, distributing or using this email in
any way.
Unauthorised use of the information contained in this email is unlawful.
If you have
received this email in error please notify us on enquir...@bca-group.com
and delete
the email from your system.
Information contained in this email can not be disclosed, copied,
distributed or used
in any way without the prior consent of the sender. Any opinions, advice
or facts
given in this email are given without warranty or the intention to enter
into an
agreement unless specifically stated and confirmed by agreement, letter
or such other
documentation signed by an authorised signatory of BCA Holdings Limited
or any of its
subsidiary companies.
Any personal information contained in this email is strictly the view of
the sender
and is in no way authorised or attributable to BCA Holdings Limited or
any of its
subsidiary companies in any way. All emails through the company gateway
are subject
to monitoring. The company cannot be held liable for any errors or
viruses contained
in this message.
BCA (438886) Headway House, Crosby Way, Farnham, Surrey GU9 7XG, England
VAT registration number: GB 188 1552 38
#####################################################################################
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#####################################################################################
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
This email and any attachments to it may contain confidential information
intended
for the addressee only. If you are not the intended addressee, you are strictly
prohibited from disclosing, copying, distributing or using this email in any
way.
Unauthorised use of the information contained in this email is unlawful. If you
have
received this email in error please notify us on enquir...@bca-group.com and
delete
the email from your system.
Information contained in this email can not be disclosed, copied, distributed
or used
in any way without the prior consent of the sender. Any opinions, advice or
facts
given in this email are given without warranty or the intention to enter into an
agreement unless specifically stated and confirmed by agreement, letter or such
other
documentation signed by an authorised signatory of BCA Holdings Limited or any
of its
subsidiary companies.
Any personal information contained in this email is strictly the view of the
sender
and is in no way authorised or attributable to BCA Holdings Limited or any of
its
subsidiary companies in any way. All emails through the company gateway are
subject
to monitoring. The company cannot be held liable for any errors or viruses
contained
in this message.
BCA (438886) Headway House, Crosby Way, Farnham, Surrey GU9 7XG, England
VAT registration number: GB 188 1552 38
#####################################################################################
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#####################################################################################
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
