The nature of OOMEs is, that they can happen in every part of the code,
that needs a new peace of memory. No one is able to write code in a way,
that can handle memory allocation failures in all places new memory is
needed.
If you run into an OOME, it is very unwise to let the JVM run along,
William Leung wrote:
> I had face the same problem, OOME sometimes "kill" tomcat connector.
>
> I setup two connectors (HTTP and AJP), while one connector was "dead", the
> other still "alive", and I could access manager/status from the "live" one
> to watch the "dead" one's status.
>
> I think i
Leon Rosenberg wrote:
> Any opinions, is that a bug in tomcat or is it inescapable after an OOME?
OOME will kill Tomcat. I have seen it struggle on after an OOME but it
always dies shortly afterwards.
You need to get a profiler (I use YourKit) and find out what is using
all the memory. Then: fix
egards
> Leon
>
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View thi
Hi,
one of my customers recently increased amount of memory they use, so
OOME are happening more often. Most of them however do no harm, since
just the request is aborted, but the container remains functional and
next request wents well (they have a throughput of >100MB per second
in young generat
