I am running Tomcat 6 AKKA 2.11 I am using Spring Webservices. I have an Application listener that listens for a ContextClosedEvent. This calls system.stop on top level actors , then system.shutdown and then an awaitTermination. After these run I get a series of errors like: SEVERE: The web application [/pois] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@79e2c065]) and a value of type [scala.concurrent.forkjoin.ForkJoinPool.Submitter] (value [scala.concurrent.forkjoin.ForkJoinPool$Submitter@7e07db1f]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
This is just one of several error messages. These posts indicate that it is fixed, but it does not appear to be fixed. On Thursday, September 20, 2012 7:52:15 AM UTC-6, √ wrote: > > Shouldn't be a problem. > > https://www.assembla.com/spaces/akka/tickets/2479 > > Cheers, > √ > > On Thu, Sep 20, 2012 at 3:45 PM, Eirik <[email protected] <javascript:>> > wrote: > >> I'm using Akka 2.0.3 on Tomcat 7.0.30 and am facing the same issues on >> shutdown. >> >> I've got a shutdown method that gets called before Tomcats >> memory-leak-detection algorithm runs. The shutdown method does: >> actorSystem.shutdown(); >> actorSystem.awaitTermination(); >> >> But Tomcat still complains: >> SEVERE: The web application [/******] created a ThreadLocal with key of >> type [akka.jsr166y.ForkJoinPool.ThreadSubmitter] (value >> [akka.jsr166y.ForkJoinPool$ThreadSubmitter@1e8b404]) and a value of type >> [akka.jsr166y.ForkJoinPool.Submitter] (value >> [akka.jsr166y.ForkJoinPool$Submitter@829a91]) but failed to remove it when >> the web application was stopped. Threads are going to be renewed over time >> to try and avoid a probable memory leak. >> >> I haven't dug deep enough at the moment to figure out if I should worry >> about this or not, but I've written some more shutdown logic just to be >> safe, that searches through threadlocals to find the ForkJoinPool$Submitter >> and removes it. This solves the issue, but shouldn't akka already have take >> care of cleaning up when I called shutdown and awaitTermination? >> >> Regards, Eirik >> >> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user >> --- >> You received this message because you are subscribed to the Google Groups >> "Akka User List" group. >> To post to this group, send email to [email protected] >> <javascript:>. >> To unsubscribe from this group, send email to >> [email protected] <javascript:>. >> Visit this group at http://groups.google.com/group/akka-user?hl=en. >> >> >> > > > > -- > Viktor Klang > > Akka Tech Lead > Typesafe <http://www.typesafe.com/> - The software stack for applications > that scale > > Twitter: @viktorklang > > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
