On 12/11/2013 7:14 AM, Christopher Schultz wrote:
3. cath IOException in a filter and set an application
attribute. Check this attribute from your monitor.
I've been considering doing this, because I can rig it so that
the error handler does not actually require any memory to run.
The problem is that sometimes OOMEs interrupt one thread and not
another. You may not catch the OOME in that thread -- it may
happen in a background thread that does not go through the
filter.
I'm not sure I understand this one. How does an IOException relate
to an OOME?
Sorry, I meant of course OutOfMemoryError. Just make sure you use as
little memory as possible during the exception handler or it will fail
itself and possibly mask the original problem.
-
You can catch an OOME in a fiter? I would not have expected that.
Off to the documentation.....
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
