https://issues.apache.org/bugzilla/show_bug.cgi?id=55533
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from Mark Thomas <ma...@apache.org> ---
The resource lookups go via JNDI and that uses the thread context class loader
to identify the correct resource set. My best guess is that a thread in the
executor was retaining a reference to the old class loader and that was messing
up the JNDI lookup.
I don't think there is anything that could be done in Tomcat to fix this. It is
a useful data point for folks that see similar issues in the future. Thanks for
doing the research and reporting back your findings.
--
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
