On 12/05/2012 18:01, Konstantin Kolinko wrote: > 2012/5/12 Jesse Farinacci <jie...@gmail.com>:
>> With the listeners all added, things are working as I expect. The >> resource is served, no error is produced. I still think this is a bug >> though.. if I open a new bug, will it be accepted? >> > > I do not know. > > If there exists a simple solution (like reopening the closed jar in > WARDirContext?) then it is worth trying. > > If there is not, then I see little wrong with resolving it as WONTFIX > and asking people to have proper configuration, but I will leave it to > others for a while to take another look and decide. > > As with enhancement requests, if there is a patch, or if there is wide > interest in it (other ways to trigger it?), the more are its chances. > > I personally have some grudge against WebappClassLoader.closeJARs() [2] > and maybe disabling it will workaround the issue (not tested) but I do > not know what actually happens here at the moment. > > [2] https://issues.apache.org/bugzilla/show_bug.cgi?id=52448 Now there is a simple, reproducible test case, I'd be happy to see a bug opened and will add it to my list of things to do for the next Tomcat release. I agree removing the leak prevention listener is a bad idea but this particular side effect is not one I would expect. I suspect it has something to do with urlCacheProtection. We'll see. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
