You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by AD <st...@gmail.com> on 2008/11/01 00:19:59 UTC
All threads (200) are currently busy
I am trying to find out after doing some load testing why tomcat is getting
hung up on some threads. Can anyone provide some info on how to track down
where the blocking is happening here? I am unable to diagnose based on this
dump..
http://pastie.org/305167
thanks
Adam
RE: All threads (200) are currently busy
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: AD [mailto:straightflush@gmail.com]
> Subject: Re: All threads (200) are currently busy
>
> Whats the best way to get the thread dump and find out what
> process is hung in the webapp ?
Since you're on a 1.6 JVM, the jstack tool from the JDK is probably the easiest. (Use jps to find the pid first.) You can also use JConsole to look at what's going on graphically.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: All threads (200) are currently busy
Posted by Bob Hall <rf...@yahoo.com>.
--- On Sun, 11/2/08 at 1:23 AM, Juha Laiho <Ju...@iki.fi> wrote:
>
> What kind of situation did you have when you took the
> thread dump in
> the original request? Could you take a thread dump at a
> such point in
> time where you are actually waiting for a request to
> complete? That
> way, at least one of the threads would have to be somewhere
> "in the
> slow section".
AD, you could add a filter that would log request/response handling
for all requests and include the thread Id and request parms info.
The log would be processed to identify requests w/o a response and
requests that took a long time to handle.
-Bob
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: All threads (200) are currently busy
Posted by Juha Laiho <Ju...@iki.fi>.
AD wrote:
> On Sat, Nov 1, 2008 at 5:25 PM, Caldarale, Charles R <
> Chuck.Caldarale@unisys.com> wrote:
>
>>> From: AD [mailto:straightflush@gmail.com]
>>> Subject: Re: All threads (200) are currently busy
>>>
>>> ah sorry, proxied through apache with mod_proxy_balancer on ajp port
>> Can you try your load test directly into Tomcat on port 8080 and eliminate
>> one variable? If that test runs satisfactorily, you'll need to check into
>> your front-end configuration.
> I did try connecting directly to 8080 on a few of the tomcat serviers in the
> cluster but the requests were just hanging. I can run the load test again
> though with apache out of the mix and see what happens.
What kind of situation did you have when you took the thread dump in
the original request? Could you take a thread dump at a such point in
time where you are actually waiting for a request to complete? That
way, at least one of the threads would have to be somewhere "in the
slow section".
--
..Juha
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: All threads (200) are currently busy
Posted by AD <st...@gmail.com>.
I did try connecting directly to 8080 on a few of the tomcat serviers in the
cluster but the requests were just hanging. I can run the load test again
though with apache out of the mix and see what happens.
Adam
On Sat, Nov 1, 2008 at 5:25 PM, Caldarale, Charles R <
Chuck.Caldarale@unisys.com> wrote:
> > From: AD [mailto:straightflush@gmail.com]
> > Subject: Re: All threads (200) are currently busy
> >
> > ah sorry, proxied through apache with mod_proxy_balancer on ajp port
>
> Can you try your load test directly into Tomcat on port 8080 and eliminate
> one variable? If that test runs satisfactorily, you'll need to check into
> your front-end configuration.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all computers.
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
RE: All threads (200) are currently busy
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: AD [mailto:straightflush@gmail.com]
> Subject: Re: All threads (200) are currently busy
>
> ah sorry, proxied through apache with mod_proxy_balancer on ajp port
Can you try your load test directly into Tomcat on port 8080 and eliminate one variable? If that test runs satisfactorily, you'll need to check into your front-end configuration.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: All threads (200) are currently busy
Posted by AD <st...@gmail.com>.
ah sorry, proxied through apache with mod_proxy_balancer on ajp port
On Sat, Nov 1, 2008 at 2:14 PM, Caldarale, Charles R <
Chuck.Caldarale@unisys.com> wrote:
> > From: AD [mailto:straightflush@gmail.com]
> > Subject: Re: All threads (200) are currently busy
> >
> > And yes these were all http requests for the web applicatoin
> > for our load test.
>
> The wasn't quite the question. Are the requests being sent through your
> httpd front end on the AJP port, or direct to Tomcat on its HTTP port
> (8080)?
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all computers.
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
RE: All threads (200) are currently busy
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: AD [mailto:straightflush@gmail.com]
> Subject: Re: All threads (200) are currently busy
>
> And yes these were all http requests for the web applicatoin
> for our load test.
The wasn't quite the question. Are the requests being sent through your httpd front end on the AJP port, or direct to Tomcat on its HTTP port (8080)?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: All threads (200) are currently busy
Posted by AD <st...@gmail.com>.
Yea the link above is the kill -QUIT output.
We do have aanother webapp connected to an ActiveMQ broker so that makes
sense. I assumed the same as you Charles, that Tomcat was "waiting" for
work, but we were running a load test at the time and the responses were
coming back slowly. Trying to nail down why Tomcat was waiting for requests
, yet wouldnt respond to any when directly connected to it. I
And yes these were all http requests for the web applicatoin for our load
test.
Adam
On Sat, Nov 1, 2008 at 11:49 AM, Mohit Anchlia <mo...@gmail.com>wrote:
> try kill -QUIT <pid>
>
> This will give you thread dump of tomcat and of course that will
> include threads associated with your webapp
> On Fri, Oct 31, 2008 at 5:22 PM, AD <st...@gmail.com> wrote:
> > Fair enough
> >
> > Tomcat 5.5, JVM 1.6, Redhat Enterprise 5, 8Gb Mem, 5Gb Heap.
> >
> > What is the best way to take a thread dump to see what processes are
> > waiting? We have a few web apps deployed and it has proven tricky for me
> to
> > narrow this down. We ran some load tests and encountered these issues.
> >
> > Whats the best way to get the thread dump and find out what process is
> hung
> > in the webapp ?
> >
> > Thx
> > Adam
> >
> > On Fri, Oct 31, 2008 at 7:31 PM, Caldarale, Charles R <
> > Chuck.Caldarale@unisys.com> wrote:
> >
> >> > From: AD [mailto:straightflush@gmail.com]
> >> > Subject: All threads (200) are currently busy
> >>
> >> First, you need to provide some environmental information: Tomcat
> version,
> >> OS, JVM version, etc.
> >>
> >> > I am trying to find out after doing some load testing why
> >> > tomcat is getting hung up on some threads.
> >>
> >> Put the blame where it belongs: you webapp is getting hung up, not
> Tomcat.
> >>
> >> Take a thread dump and see where the threads are stuck.
> >>
> >> - Chuck
> >>
> >>
> >> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> >> MATERIAL and is thus for use only by the intended recipient. If you
> received
> >> this in error, please contact the sender and delete the e-mail and its
> >> attachments from all computers.
> >>
> >> ---------------------------------------------------------------------
> >> To start a new topic, e-mail: users@tomcat.apache.org
> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: users-help@tomcat.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: All threads (200) are currently busy
Posted by Mohit Anchlia <mo...@gmail.com>.
try kill -QUIT <pid>
This will give you thread dump of tomcat and of course that will
include threads associated with your webapp
On Fri, Oct 31, 2008 at 5:22 PM, AD <st...@gmail.com> wrote:
> Fair enough
>
> Tomcat 5.5, JVM 1.6, Redhat Enterprise 5, 8Gb Mem, 5Gb Heap.
>
> What is the best way to take a thread dump to see what processes are
> waiting? We have a few web apps deployed and it has proven tricky for me to
> narrow this down. We ran some load tests and encountered these issues.
>
> Whats the best way to get the thread dump and find out what process is hung
> in the webapp ?
>
> Thx
> Adam
>
> On Fri, Oct 31, 2008 at 7:31 PM, Caldarale, Charles R <
> Chuck.Caldarale@unisys.com> wrote:
>
>> > From: AD [mailto:straightflush@gmail.com]
>> > Subject: All threads (200) are currently busy
>>
>> First, you need to provide some environmental information: Tomcat version,
>> OS, JVM version, etc.
>>
>> > I am trying to find out after doing some load testing why
>> > tomcat is getting hung up on some threads.
>>
>> Put the blame where it belongs: you webapp is getting hung up, not Tomcat.
>>
>> Take a thread dump and see where the threads are stuck.
>>
>> - Chuck
>>
>>
>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
>> MATERIAL and is thus for use only by the intended recipient. If you received
>> this in error, please contact the sender and delete the e-mail and its
>> attachments from all computers.
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: All threads (200) are currently busy
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: AD [mailto:straightflush@gmail.com]
> Subject: Re: All threads (200) are currently busy
>
> the pastie link that I sent in my original post which was a
> kill -QUIT when the problem was happening.
Sorry, didn't realize that was a link to something useful.
There are a few threads waiting for input on various sockets, but other than that, Tomcat is idle, just waiting for work to show up. One thread is listening to httpd; is that where most (or all?) of your requests come from? Should there really be two threads listening for ActiveMQ?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: All threads (200) are currently busy
Posted by AD <st...@gmail.com>.
the pastie link that I sent in my original post which was a kill -QUIT when
the problem was happening.
On Fri, Oct 31, 2008 at 10:49 PM, Caldarale, Charles R <
Chuck.Caldarale@unisys.com> wrote:
> > From: AD [mailto:straightflush@gmail.com]
> > Subject: Re: All threads (200) are currently busy
> >
> > will it provide more info than what is in the kill -QUIT from
> > above ?
>
> What "above" are you talking about?
>
> The jstack tool with the -l option provides the most information; kill -3
> is very similar, but omits the extra locking info which may be quite useful
> in your situation.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all computers.
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
RE: All threads (200) are currently busy
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: AD [mailto:straightflush@gmail.com]
> Subject: Re: All threads (200) are currently busy
>
> will it provide more info than what is in the kill -QUIT from
> above ?
What "above" are you talking about?
The jstack tool with the -l option provides the most information; kill -3 is very similar, but omits the extra locking info which may be quite useful in your situation.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: All threads (200) are currently busy
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
AD,
>> On Fri, Oct 31, 2008 at 9:43 PM, Litton, Tom - CEPM
>> <To...@cepm-us.com>wrote:
>>
>>> If you do a kill -3 on the process it will dump the stack trace to the
>>> standard output stream.
AD wrote:
> will it provide more info than what is in the kill -QUIT from above ?
FYI "kill -3" == "kill -QUIT". UNIX signal 3 /is/ QUIT.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkkQxr8ACgkQ9CaO5/Lv0PAF/ACdHkxwf/zQkDFgD0KTKnII3j4m
ZBYAoIpqPJsYBx2iurWwz5rL+QklpCek
=koF9
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: All threads (200) are currently busy
Posted by AD <st...@gmail.com>.
will it provide more info than what is in the kill -QUIT from above ? I am
still struggling a bit to find out what process/library is blocking the
thread in my app...
Adam
On Fri, Oct 31, 2008 at 9:43 PM, Litton, Tom - CEPM
<To...@cepm-us.com>wrote:
> If you do a kill -3 on the process it will dump the stack trace to the
> standard output stream.
>
> Sent from my iPhone
>
>
> On Oct 31, 2008, at 7:23 PM, "AD" <st...@gmail.com> wrote:
>
> Fair enough
>>
>> Tomcat 5.5, JVM 1.6, Redhat Enterprise 5, 8Gb Mem, 5Gb Heap.
>>
>> What is the best way to take a thread dump to see what processes are
>> waiting? We have a few web apps deployed and it has proven tricky for me
>> to
>> narrow this down. We ran some load tests and encountered these issues.
>>
>> Whats the best way to get the thread dump and find out what process is
>> hung
>> in the webapp ?
>>
>> Thx
>> Adam
>>
>> On Fri, Oct 31, 2008 at 7:31 PM, Caldarale, Charles R <
>> Chuck.Caldarale@unisys.com> wrote:
>>
>> From: AD [mailto:straightflush@gmail.com]
>>>> Subject: All threads (200) are currently busy
>>>>
>>>
>>> First, you need to provide some environmental information: Tomcat
>>> version,
>>> OS, JVM version, etc.
>>>
>>> I am trying to find out after doing some load testing why
>>>> tomcat is getting hung up on some threads.
>>>>
>>>
>>> Put the blame where it belongs: you webapp is getting hung up, not
>>> Tomcat.
>>>
>>> Take a thread dump and see where the threads are stuck.
>>>
>>> - Chuck
>>>
>>>
>>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
>>> MATERIAL and is thus for use only by the intended recipient. If you
>>> received
>>> this in error, please contact the sender and delete the e-mail and its
>>> attachments from all computers.
>>>
>>> ---------------------------------------------------------------------
>>> To start a new topic, e-mail: users@tomcat.apache.org
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>
> ----------------------------------------------------------------------
> The information contained in this transmission is intended only for
> the personal and confidential use of the designated recipients named
> herein. If the reader of this transmission is not the intended
> recipient or an agent responsible for delivering it to the intended
> recipient, you are hereby notified that you have received this
> transmission in error, and that any review, dissemination,
> distribution, or copying of this transmission is strictly prohibited.
> If you have received this communication in error, please notify the
> sender and return and delete the original transmission immediately.
> Thank you.
>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: All threads (200) are currently busy
Posted by "Litton, Tom - CEPM" <To...@cepm-us.com>.
If you do a kill -3 on the process it will dump the stack trace to the
standard output stream.
Sent from my iPhone
On Oct 31, 2008, at 7:23 PM, "AD" <st...@gmail.com> wrote:
> Fair enough
>
> Tomcat 5.5, JVM 1.6, Redhat Enterprise 5, 8Gb Mem, 5Gb Heap.
>
> What is the best way to take a thread dump to see what processes are
> waiting? We have a few web apps deployed and it has proven tricky
> for me to
> narrow this down. We ran some load tests and encountered these
> issues.
>
> Whats the best way to get the thread dump and find out what process
> is hung
> in the webapp ?
>
> Thx
> Adam
>
> On Fri, Oct 31, 2008 at 7:31 PM, Caldarale, Charles R <
> Chuck.Caldarale@unisys.com> wrote:
>
>>> From: AD [mailto:straightflush@gmail.com]
>>> Subject: All threads (200) are currently busy
>>
>> First, you need to provide some environmental information: Tomcat
>> version,
>> OS, JVM version, etc.
>>
>>> I am trying to find out after doing some load testing why
>>> tomcat is getting hung up on some threads.
>>
>> Put the blame where it belongs: you webapp is getting hung up, not
>> Tomcat.
>>
>> Take a thread dump and see where the threads are stuck.
>>
>> - Chuck
>>
>>
>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
>> PROPRIETARY
>> MATERIAL and is thus for use only by the intended recipient. If you
>> received
>> this in error, please contact the sender and delete the e-mail and
>> its
>> attachments from all computers.
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
----------------------------------------------------------------------
The information contained in this transmission is intended only for
the personal and confidential use of the designated recipients named
herein. If the reader of this transmission is not the intended
recipient or an agent responsible for delivering it to the intended
recipient, you are hereby notified that you have received this
transmission in error, and that any review, dissemination,
distribution, or copying of this transmission is strictly prohibited.
If you have received this communication in error, please notify the
sender and return and delete the original transmission immediately.
Thank you.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: All threads (200) are currently busy
Posted by AD <st...@gmail.com>.
Fair enough
Tomcat 5.5, JVM 1.6, Redhat Enterprise 5, 8Gb Mem, 5Gb Heap.
What is the best way to take a thread dump to see what processes are
waiting? We have a few web apps deployed and it has proven tricky for me to
narrow this down. We ran some load tests and encountered these issues.
Whats the best way to get the thread dump and find out what process is hung
in the webapp ?
Thx
Adam
On Fri, Oct 31, 2008 at 7:31 PM, Caldarale, Charles R <
Chuck.Caldarale@unisys.com> wrote:
> > From: AD [mailto:straightflush@gmail.com]
> > Subject: All threads (200) are currently busy
>
> First, you need to provide some environmental information: Tomcat version,
> OS, JVM version, etc.
>
> > I am trying to find out after doing some load testing why
> > tomcat is getting hung up on some threads.
>
> Put the blame where it belongs: you webapp is getting hung up, not Tomcat.
>
> Take a thread dump and see where the threads are stuck.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all computers.
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
RE: All threads (200) are currently busy
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: AD [mailto:straightflush@gmail.com]
> Subject: All threads (200) are currently busy
First, you need to provide some environmental information: Tomcat version, OS, JVM version, etc.
> I am trying to find out after doing some load testing why
> tomcat is getting hung up on some threads.
Put the blame where it belongs: you webapp is getting hung up, not Tomcat.
Take a thread dump and see where the threads are stuck.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org