Re: help analyzing thread dump for Tomcat 7.0.23 issue

2012-01-04 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike, On 1/2/12 9:55 PM, Mike Wertheim wrote: > On Mon, Jan 2, 2012 at 3:09 PM, Christopher Schultz >> What were those 4 RUNNABLE threads doing? > > They were processing POST requests from the client with a somewhat > large data payload. > > Here's

Re: help analyzing thread dump for Tomcat 7.0.23 issue

2012-01-03 Thread Mike Wertheim
On Mon, Jan 2, 2012 at 6:55 PM, Mike Wertheim wrote: > On Mon, Jan 2, 2012 at 3:09 PM, Christopher Schultz > wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Mike, >> >> On 12/29/11 9:01 PM, Mike Wertheim wrote: >>> I did a stack dump on 7.0.23 when it was in its messed up state.

Re: help analyzing thread dump for Tomcat 7.0.23 issue

2012-01-03 Thread Janne Jalkanen
>> What were those 4 RUNNABLE threads doing? > > They were processing POST requests from the client with a somewhat > large data payload. Just wanted to pop in and say that my app does also get large POST requests AND uses APR AND has problems on 7.0.23. Perhaps my FD leak is related to this?

Re: help analyzing thread dump for Tomcat 7.0.23 issue

2012-01-02 Thread Mike Wertheim
On Mon, Jan 2, 2012 at 3:09 PM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Mike, > > On 12/29/11 9:01 PM, Mike Wertheim wrote: >> I did a stack dump on 7.0.23 when it was in its messed up state. >> No threads are blocked on critical sections of my app. > > Tha

RE: help analyzing thread dump for Tomcat 7.0.23 issue

2012-01-02 Thread Caldarale, Charles R
> From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Subject: Re: help analyzing thread dump for Tomcat 7.0.23 issue > "Runnable" means that the thread is actually doing something. Or that the thread is out in native code - and possibly stuck there. The

Re: help analyzing thread dump for Tomcat 7.0.23 issue

2012-01-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike, On 12/29/11 9:01 PM, Mike Wertheim wrote: > I did a stack dump on 7.0.23 when it was in its messed up state. > No threads are blocked on critical sections of my app. That's good. > For the port 8080 connector, there are 196 threads in "waiting

Re: help analyzing thread dump for Tomcat 7.0.23 issue

2011-12-31 Thread Mike Wertheim
On Sat, Dec 31, 2011 at 12:53 PM, Pid * wrote: > On 31 Dec 2011, at 16:14, Mike Wertheim wrote: > >> I'm using the APR Connector. >> >> Here's my server.xml: >> >> >> >> >>  > SSLEngine="on" /> >>   >>  > className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" >> /> > > No memor

Re: help analyzing thread dump for Tomcat 7.0.23 issue

2011-12-31 Thread Pid *
On 31 Dec 2011, at 16:14, Mike Wertheim wrote: > I'm using the APR Connector. > > Here's my server.xml: > > > > > SSLEngine="on" /> > > className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" > /> No memory leak prevention listeners? > > type="org.apac

Re: help analyzing thread dump for Tomcat 7.0.23 issue

2011-12-31 Thread Mike Wertheim
I'm using the APR Connector. Here's my server.xml: On Sat, Dec 31, 2011 at 5:39 AM, Pid wrote: > On 30/12/2011 02:01, Mike Wertheim wrote: >> I have an app that runs on Tomcat 7.0.21 and APR 1.4.7

Re: help analyzing thread dump for Tomcat 7.0.23 issue

2011-12-31 Thread Pid
On 30/12/2011 02:01, Mike Wertheim wrote: > I have an app that runs on Tomcat 7.0.21 and APR 1.4.7 just fine. The > app serves both SSL and non-SSL traffic. SSL traffic makes up roughly > 1% of the overall traffic. The Connectors for SSL and non-SSL both > use the default value (200) for maxThre