Yeah, I saw that. I don't know if they manually clean the ITL's or not, but they're definitely getting cleaned up. Perhaps trying it with Jetty (unless someone knows that they also clean up after themselves) might show that these references leak?
On Wed, May 26, 2010 at 1:18 AM, Martijn Dashorst <[email protected]> wrote: > The newest tomcat has improved permgen cleanup which they backported > from tomcat 7 iiuc. > > Martijn > > On Wed, May 26, 2010 at 3:10 AM, James Carman > <[email protected]> wrote: >> I've done some playing with Tomcat undeploy and it does appear that >> the ITL reference is cleared (perhaps Sun/Oracle/Sunacle should close >> the "bug"?). However, this does not make the ITL implementation >> valid, IMHO. It doesn't work (out of the box) for the preferred >> method of executing asynchronous tasks, which is to use a thread pool. >> >> On Tue, May 25, 2010 at 6:38 PM, Alex Objelean <[email protected]> >> wrote: >>> >>> Jeremy, I've tried with redeploy... same story. I'm not insisting on >>> bringing >>> the issue back. If is the willing of the majority, I'm ok. It is just to >>> help me understand something that I'm not find that obvious. >>> >>> Alex >>> -- >>> View this message in context: >>> http://apache-wicket.1842946.n4.nabble.com/vote-Revert-WICKET-2846-tp2226987p2230845.html >>> Sent from the Wicket - Dev mailing list archive at Nabble.com. >>> >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >
