-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeffrey,
On 4/13/2010 10:44 AM, Jeffrey Janner wrote: > I had a connector go from minimal connections (restart) to all threads > hung overnight. > > The current thread dump shows the threads as follows: > > "http-172.16.27.1-443-150" daemon prio=6 tid=0x66793800 nid=0xe43c in > Object.wait() [0x7063f000] > > java.lang.Thread.State: WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > - waiting on <0x1a924f00> (a > org.apache.tomcat.util.net.AprEndpoint$Worker) I'm pretty sure these threads are considered idle. Are you able to make a request on port 443 and have it serviced? > Other connectors are running OK, though some also show > threads in the same state. All other threads look normal. This has one > customer's app hung, but others in the Tomcat instance are working just > fine. Any help on where to start looking here? The connectors are global for the entire app server, so if any webapps are accessible, they should all be accessible (unless this is the only webapp that requires SSL, in which case a dead SSL connector would certainly affect only that one webapp). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEkWUACgkQ9CaO5/Lv0PAuIgCfULZw2F0zb+CBMWvJVUC8JIHt iuMAoJM6Cs2dC7ufRfEA/13Z513NjfdZ =WSuM -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
