-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felix,
On 5/4/2011 1:07 AM, Felix Schumacher wrote:
> It could've been the garbage collector itself. Just yesterday I had
> an oom on permgen, which lead to a major-gc loop. I could see the
> loop nicely as I had enabled logging of gc activity with
>
"Christopher Schultz" schrieb:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Mark,
>
>On 5/3/2011 10:52 AM, Mark Thomas wrote:
>> On 03/05/2011 15:46, André Warnier wrote:
>>> Mark Thomas wrote:
On 03/05/2011 15:22, Christopher Schultz wrote:
> All,
>
> Moments ago in our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 5/3/2011 10:52 AM, Mark Thomas wrote:
> On 03/05/2011 15:46, André Warnier wrote:
>> Mark Thomas wrote:
>>> On 03/05/2011 15:22, Christopher Schultz wrote:
All,
Moments ago in our development environment, our webapp suffered an
On 03/05/2011 15:46, André Warnier wrote:
> Mark Thomas wrote:
>> On 03/05/2011 15:22, Christopher Schultz wrote:
>>> All,
>>>
>>> Moments ago in our development environment, our webapp suffered an OOME
>>> after many re-reployments (we know we have an undeploy-related leak).
>>> When attempting to
Mark Thomas wrote:
On 03/05/2011 15:22, Christopher Schultz wrote:
All,
Moments ago in our development environment, our webapp suffered an OOME
after many re-reployments (we know we have an undeploy-related leak).
When attempting to bounce Tomcat, the shutdown failed and I took a
thread dump wh
On 03/05/2011 15:22, Christopher Schultz wrote:
> All,
>
> Moments ago in our development environment, our webapp suffered an OOME
> after many re-reployments (we know we have an undeploy-related leak).
> When attempting to bounce Tomcat, the shutdown failed and I took a
> thread dump which includ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
Moments ago in our development environment, our webapp suffered an OOME
after many re-reployments (we know we have an undeploy-related leak).
When attempting to bounce Tomcat, the shutdown failed and I took a
thread dump which included the one no
