******************************* NOTICE *********************************
This message is intended for the use of the individual or entity to which
it is addressed and may contain information that is privileged,
confidential, and exempt from disclosure under applicable law. If the
reader of this message is not the intended recipient or the employee or
agent responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution, or copying
of this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by reply or by
telephone (call us collect at 512-343-9100) and immediately delete this
message and all its attachments.
--- Begin Message ---
Hi Chris -
Sorry I was extremely clear. My config has each customer in a separate service
structure, so each get his own set of connectors (IPs). Yes, I am unable to
get a response on this specific IP/port combo. All other connectors were
responding and all of those apps were working fine, from what I could tell.
The Tomcat Manager only showed 4 sessions for this host when I started, and
that eventually dropped to 1, but I could never get a response from the app.
After a restart, I did a connect, and immediately had 7 threads start up and
apparently end in the same state (at least it looks the same in jconsole). I
was able to navigate the app and never had the thread count increase. Every
check on the thread states showed the same, though the Total blocked/Total
Waited counters keep increasing.
The really interesting thing is that over more than an hour with virtually no
traffic, should not some of the threads started shutting down?
Jeff
-----Original Message-----
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Tuesday, April 13, 2010 10:45 AM
To: Tomcat Users List
Subject: Re: Hung threads
-----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
--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
