[Bug 57939] Classloader leak in org.apache.naming.ContextBindings

2015-05-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=57939 Mark Thomas changed: What|Removed |Added Resolution|--- |INVALID Status|REOPENED

[Bug 57939] Classloader leak in org.apache.naming.ContextBindings

2015-05-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=57939 Rainer Jung changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[Bug 57939] Classloader leak in org.apache.naming.ContextBindings

2015-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=57939 Mark Thomas changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 57939] Classloader leak in org.apache.naming.ContextBindings

2015-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=57939 --- Comment #1 from Mark Thomas --- This is a symptom of a different problem. It can happen if an uncaught exception is thrown by an earlier LifecycleListener. You'll probably want to speak to your clients to find out what went wrong that trigg