Scott Ferguson wrote (2008-11-26 16:53):
>
> On Nov 24, 2008, at 11:08 PM, Mattias Jiderhamn wrote:
>
>> I'm still battling this PermGen leak and frankly I'm really starting
>> to doubt that I know what I'm doing anymore. I'd be very happy if
>> anyone would care to explain that to me...
>>
>> Sinc
I trick that I use to trouble shoot perm gen memory leak involves using
jconsole and , jmap, and jhat. I would attach to resin with jconsole, then
reload the webapp a few times to trigger the perm gen leak. That I will
stop the webapp completely, and then go to the memory tab to trigger some
full
On Jan 9, 2009, at 12:22 AM, Mattias Jiderhamn wrote:
> Scott Ferguson wrote (2008-11-26 16:53):
>>
>> Thanks.
>>
>> Right now, our code base is a bit stuck due to the WebBeans/OSGi
>> upgrade (for Resin 4.0.0, was 3.2.2). Once that's cleaned up and I
>> can put up a snapshot I can take a look.
Thanks much, guys, for the replies.
We've arrived at the same conclusion that Scott suggests - a GB for the
heap and the other GB for the product (roughly) of the threads and the
stack size in our windows 32-bit environment.
Now it's an exercise in testing the actual -Xss size that we want to r
