I'd like to thank everyone involved,
as many of you suspected it turned out to be an infinite loop in a
component of our webapp, i've tracked the issue down to the places
where it is most possible and gave it over to the owner of the
component.
Thank all of you for great help finding it !
Leon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leon,
Leon Rosenberg wrote:
> The last thing I can imagine is that the request somehow gets
> redirected or forwarded infinitely during processing, but is not
> leaving tomcat entirely and just reenters the processing, keeping the
> outer request obje
> From: Leon Rosenberg [mailto:rosenberg.l...@googlemail.com]
> Subject: Re: Memory Leak(?) causing tomcat to store 57610801
> tomcat objects in ONE request
>
> The other explanation would be a direct infinite loop in
> the application, but that should also be visible in the
>
A small update on the matter:
I've managed to track it down, but the details are rather application
specific, so I don't want to bore you, but the scenario looks as
follows:
- something posts a rather normal looking request to an url that is
yet supported but obsolete (should be actually served b
> From: Leon Rosenberg [mailto:rosenberg.l...@googlemail.com]
>
> I was recently hunting what I thought to be a memory leak in our
> application. What happens is that the Old Gen Space is running full at
> once and then tomcat freezes
> because java is busy with Full GC all the time. I've managed t
2009/1/10 Caldarale, Charles R :
>> From: Leon Rosenberg [mailto:rosenberg.l...@googlemail.com]
>> Subject: Memory Leak(?) causing tomcat to store 57610801
>> tomcat objects in ONE request
>>
>> HOW can it actually happen that a response object
>> contains 8
> From: Leon Rosenberg [mailto:rosenberg.l...@googlemail.com]
> Subject: Memory Leak(?) causing tomcat to store 57610801
> tomcat objects in ONE request
>
> HOW can it actually happen that a response object
> contains 8.000.000 mime headers?
Must be a very productive servl
Hi,
I was recently hunting what I thought to be a memory leak in our
application. What happens is that the Old Gen Space is running full at
once and then tomcat freezes
because java is busy with Full GC all the time. I've managed to create
a memory dump shortly before the crash and the top5 looked
