https://bz.apache.org/bugzilla/show_bug.cgi?id=57939
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|REOPENED |RESOLVED
--- Comment #4 from Mark Thomas <ma...@apache.org> ---
The original fix (log a lifecycle listener exception and continue) didn't work
since lifecycle exceptions are expected to be fatal.
I've taken a longer look at the code and an exception in a lifcycle listener is
still the only way I can see this happening. That should result in at least one
log entry with a stack trace and the web application ending up in the failed
state. Under these conditions, a memory leak isn't a surprise and it is the
root cause (of the failed lifecycle listener) that needs to be addressed.
For now I am reslving this as invalid but please feel free to re-open this
issue if any of the following are the case:
- no stack trace is logged (with default logging levels)
- the web application is not marked as failed
- the error is recoverable but the memory leak remains
For any of these please provide the exact steps to reproduce the error form a
clean install of the latest stable Tomcat 8 release. If a web applciation is
required to reproduce it, please keep the web application as simple as
possible.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
