On 09/07/2010 09:05 AM, John Baker wrote:
On Tuesday 07 September 2010 06:28:33 you wrote:
On 09/06/2010 11:59 PM, John Baker wrote:
What's jk_maintain?
Function that maintains the workers
(closes excess connections inactive for a long time)
Anyhow, like Rainer said, if that's the case
you should have something like this in the log (DEBUG)
... Shutdown socket 123 and read 123 lingering bytes in 2 sec.
Is this what we're looking for? There's a lot of it in the logs during the
period in which I switched on 'trace'.
[Mon Sep 06 15:05:18.128 2010] [24061:1404667232] [debug]
jk_shutdown_socket::jk_connect.c (732): Shutdown socket 158 and rea 0
lingering bytes
If so, what does this mean and how do I solve the problem?
It means that socket shutdown failed.
Do you have firewall between mod_jk and JBoss or some non-standard
network driver (e.g running under some VM)?
This can cause network FIN packet not getting transmitted over it
since we issued socket shutdown, but the other side didn't react on
that message.
What kind of connector is on the JBoss side. Java or APR?
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
