On 04.08.2011 19:44, Dante Bell wrote:
> Hi Igor & Chuck,
>
> I don't think I specified, but they are running prefork 2.2 (updated
> blog to show this:
> http://wp.me/plPvN-ai) So cachesize has been deprecated and is now
> connection_pool_size. The notes state that when running Apache prefork,
> t
this url for config files and for the thread dump:
>> http://wp.me/plPvN-ai
>>
>> I've check bugzilla and this issue seems to be different to the other
>> bugs when there was a thread issue.
>>
>> Thanks!
>>
>> On 08/03/2011 10:44 AM, Caldara
hread dump:
>> http://wp.me/plPvN-ai
>>
>> I've check bugzilla and this issue seems to be different to the other
>> bugs when there was a thread issue.
>>
>> Thanks!
>>
>> On 08/03/2011 10:44 AM, Caldarale, Charles R wrote:
>>>> From
ead dump:
> http://wp.me/plPvN-ai
>
> I've check bugzilla and this issue seems to be different to the other
> bugs when there was a thread issue.
>
> Thanks!
>
> On 08/03/2011 10:44 AM, Caldarale, Charles R wrote:
> >> From: Dante Bell [mailto:dantepasqu...@cocoan
bugs when there was a thread issue.
Thanks!
On 08/03/2011 10:44 AM, Caldarale, Charles R wrote:
>> From: Dante Bell [mailto:dantepasqu...@cocoanet.us]
>> Subject: Re: Tomcat not releasing threads on Solaris 10
>> Seems that all threads are waiting:
>> java.lang.Thread.State:
> From: Dante Bell [mailto:dantepasqu...@cocoanet.us]
> Subject: Re: Tomcat not releasing threads on Solaris 10
> Seems that all threads are waiting:
> java.lang.Thread.State: WAITING (on object monitor)
It's the rest of the trace for each thread that would be interesting.
>
I do have a stack dump, but don't have enough experience to understand
it. Seems that all threads are waiting:
> java.lang.Thread.State: WAITING (on object monitor)
Size of compressed stack dump is 20k. Is that OK to attach so someone
can help look at it?
Danté
On 08/03/2011 08:44 AM, Caldara
> From: Dante Bell [mailto:dantepasqu...@cocoanet.us]
> Subject: Tomcat not releasing threads on Solaris 10
> In their stress test, tomcat is not killing/reclaiming threads fast
> enough and eventually (after 3 hours) it runs out of threads
Tomcat does not create arbitrary, temporary threads, no
