The issue is still open http://code.google.com/p/guava-libraries/issues/detail?id=92
indeed there is a memory leak. As workarounds goes I used o) Thread "unleaker" - basically a ServletContextListener that finds any Finalizer Threads and clears the "bad" references. The WebAppCL is clear to be GCed but the Finalizer thread sticks around until the perm gen gets full. I don't like it. o) A custom Guice distribution that has an explicit method to shutdown. This is what I am currently using. imho it would not hurt to have an explicit shutdown method in the official version. Like injector.stopFinalizer(); for those of us who can't restart-to-redeploy. It's better to have one more method than one more memory leak. Cheers Alen On 24 mar., 18:25, Vojtěch Krása <[email protected]> wrote: > Hi, > > i have problem on tomcat 6.0 even with clean Wicket+Guice project > fromhttp://jweekend.co.uk/dev/LegUp... > > tomcat log: > SEVERE: A web application appears to have started a thread named > [com.google.inject.internal.Finalizer] but has failed to stop it. This is > very likely to create a memory leak. > it seems like an old issue... is there any solutions? > > Thanks. -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
