You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Gr...@pfizer.com on 2004/02/23 17:37:38 UTC

jk2 buglets II


We seem to have another buglet with mod_jk2 2.0.2.  We seem to be unable to
recreate the bug using ab, but when one of our busiest servers has been
running for a few hours we get apache children "stuck" (at times upto 100
children are blocked, which is how we found the issue as the server appeared
slow).  Looking at server-status we the stalled children appear as:

1-0	18136	1/426/426	W 	0.99	1660	0	0.3	1.40
1.40 	xxxxxx	xxxxxx	GET /homepage/components/GetTime.jsp HTTP/1.1

The time since last request (SS in this case 1660) goes up as you would
expect, yet this is the 2nd slot child. Graceful restarts do not help.  The
child remains in an apparent "W" (write state).

This only happens to JK2 served content.  Truss reveals:

# truss -p 18136
read(39, 0x00505820, 4)         (sleeping...)
signotifywait()                 (sleeping...)
lwp_sema_wait(0xFE30DE60)       (sleeping...)


(etc ......)

Any ideas on debugging this?  

This bug is present in CVS and from 2.0.2.

Thanks again. (I will shut up soon!)

Greg Cope
GCS Ltd
Assign to: CIT, Sandwich - ISG
Phone: (44) 01304 642040
Fax: (44) 01304 652118

LEGAL NOTICE
     
Unless expressly stated otherwise, this message is confidential and may be
privileged. It is intended for the addresee(s) only. Access to this e-mail
by anyone else is unauthorised. If you are not an addressee, any disclosure
or copying of the contents of this e-mail or any action taken (or not taken)
in reliance on it is unauthorised and may be unlawful. If you are not an
addressee, please inform the sender immediately.
     
Pfizer Limited is registered in England under No. 526209 with its registered
office at Ramsgate Road, Sandwich, Kent CT13 9NJ

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Re: jk2 buglets II

Posted by David Rees <dr...@greenhydrant.com>.
Greg.Cope@pfizer.com wrote, On 2/23/2004 8:37 AM:
> We seem to have another buglet with mod_jk2 2.0.2.  We seem to be unable to
> recreate the bug using ab, but when one of our busiest servers has been
> running for a few hours we get apache children "stuck" (at times upto 100
> children are blocked, which is how we found the issue as the server appeared
> slow).

Does restarting the Tomcat instance free up the stuck processes?

-Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Re: jk2 buglets II

Posted by Henri Gomez <hg...@apache.org>.
Greg.Cope@pfizer.com wrote:

> 
> We seem to have another buglet with mod_jk2 2.0.2.  We seem to be unable to
> recreate the bug using ab, but when one of our busiest servers has been
> running for a few hours we get apache children "stuck" (at times upto 100
> children are blocked, which is how we found the issue as the server appeared
> slow).  Looking at server-status we the stalled children appear as:
> 
> 1-0	18136	1/426/426	W 	0.99	1660	0	0.3	1.40
> 1.40 	xxxxxx	xxxxxx	GET /homepage/components/GetTime.jsp HTTP/1.1
> 
> The time since last request (SS in this case 1660) goes up as you would
> expect, yet this is the 2nd slot child. Graceful restarts do not help.  The
> child remains in an apparent "W" (write state).
> 
> This only happens to JK2 served content.  Truss reveals:
> 
> # truss -p 18136
> read(39, 0x00505820, 4)         (sleeping...)
> signotifywait()                 (sleeping...)
> lwp_sema_wait(0xFE30DE60)       (sleeping...)
> 
> 
> (etc ......)
> 
> Any ideas on debugging this?  
> 
> This bug is present in CVS and from 2.0.2.
> 
> Thanks again. (I will shut up soon!)

Which Tomcat on the remote side ?

3.3, 4.0, 4.1, 5.0 ?


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org