Guys,
just wondering..
The original issue of the OP was to be notified ASAP when an OOM occurs.
And he indicated that an OOM resulted in a message in the logs.
So, "something" is already catching the OOM exception, to write this line in
the logs.
On the other hand, there is ample literature available that seems to indicate that any
method for trying to recover from (or even do something worthwhile after) an OOM is
ultimately flawed and unreliable.
Whilst I am in awe of the various solutions proposed so far (and of their developers),
would it, in this case, not be simpler to pipe the log through a simple filter which
catches the OOM log message and warns the OP accordingly ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
