Thanks, it wasnt clear to me whether it was ajp/nio/http or otherwise,
but if a straight upgrade has potential I will add it to the battery of
options.
Caldarale, Charles R wrote:
From: ultan ocarroll [mailto:ultan.ocarr...@corp.aol.com]
Subject: Re: MemoryLeak Problem with
> From: ultan ocarroll [mailto:ultan.ocarr...@corp.aol.com]
> Subject: Re: MemoryLeak Problem with ThreadWithAttributes
>
> Thought I'd try one last time : was there any resolution or guidance on
> this ? Any help would be very much appreciated.
Since it appears the code in
Thought I'd try one last time : was there any resolution or guidance on
this ? Any help would be very much appreciated.
Thread ID 192899
users Digest of: thread.192899
MemoryLeak Problem with ThreadWithAttributes
192899 by: Hennig, Patrick
192916 by: Caldarale, Charles R
Hi,
Please help !
I'm having exactly the same issue here, with 5.5.27, in a production
application, and close to pulling my hair out now !
I see the ThreadWithAttributes filled with 5m xalan ElementImpl objects
(my UI is generated using XSL) in one heap dump I have. Like Patrick,
the OoM ha
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: MemoryLeak Problem with ThreadWithAttributes
>
> Back in 2003, Remy makes a claim that almost sounds like thData is
> deprecated and unused. I'm interested in what you find.
It does appear to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 3/16/2009 4:51 PM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>> Subject: Re: MemoryLeak Problem with ThreadWithAttributes
>>
>> The current version of ThreadWit
> From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
> Subject: RE: MemoryLeak Problem with ThreadWithAttributes
>
> I'm still chasing what the array is used for.
This is getting weird. The only usage of the thData array in 5.5.15 is only
two slots long. S
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: MemoryLeak Problem with ThreadWithAttributes
>
> The current version of ThreadWithAttributes doesn't have any
> methods with locals of type Object[]
These aren't local variables, these ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 3/16/2009 2:00 PM, Caldarale, Charles R wrote:
> You need to look
> inside the java.lang.Object array that this particular thread is
> holding and see what the type of object in the array is. That should
> help to narrow down where they're
> From: Hennig, Patrick [mailto:phen...@l1id.com]
> Subject: RE: MemoryLeak Problem with ThreadWithAttributes
> The Tomcat Level is 5.5.15.
That's over three years old. The first thing I'd do is move up to the current
5.5.27.
> In one of the HeapDumps i see 25 Thread
e, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Tuesday, March 10, 2009 8:55 PM
To: Tomcat Users List
Subject: RE: MemoryLeak Problem with ThreadWithAttributes
> From: Hennig, Patrick [mailto:phen...@l1id.com]
> Subject: RE: MemoryLeak Problem with ThreadWithAttributes
>
> (Dont`t know e
> From: Hennig, Patrick [mailto:phen...@l1id.com]
> Subject: RE: MemoryLeak Problem with ThreadWithAttributes
>
> (Dont`t know exactly, what you mean by "Tomcat Level")
5.5.?? Fill in the question marks.
> redirectPort="8443" protocol="AJP/1.3&q
ping,
Patrick
<<<<<<<<<<<<<<<<< server.xml >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<<<<<<<<<<<<<<<
> From: Hennig, Patrick [mailto:phen...@l1id.com]
> Subject: MemoryLeak Problem with ThreadWithAttributes
>
> Catalina_Opts is setted to:
> -Xms512m -Xmx768m.
That should be CATALINA_OPTS, not Catalina_Opts, in case you're running on a
system where the case of environment variable names matters
14 matches
Mail list logo
