THOUGHTSTORMING: Investigate possibility of quick clean shutdown of threads after ActorSystem.shutdown completes.
Might have to loop over dispatchers and terminate them
Leave a comment
on 2012-10-27 00:28 *
By viktorklang
Summary changed from Investigate possibility of quick clean shutdown of threads after ActorSystem.shutdown completes. to THOUGHTSTORMING: Investigate possibility of quick clean shutdown of threads after ActorSystem.shutdown completes.
on 2012-10-27 00:28 *
By viktorklang
Summary changed from Investigate possibility of quick clean shutdown of threads after ActorSystem.shutdown completes. to THOUGHTSTORMING: Investigate possibility of quick clean shutdown of threads after ActorSystem.shutdown completes.
on 2012-11-02 13:11 *
By worufuramo
This issue may produce OOM exception when running akka in tomcat and doing multiple redeploys.
https://www.assembla.com/spaces/akka/comments/2672/create_ticket?comment=189640183#comment:189640183
https://www.assembla.com/spaces/akka/comments/2672/create_ticket?comment=189640183#comment:189640183
on 2012-11-02 14:31 *
By viktorklang
worufuramo: Is that confirmed, i.e. can you get it to OOME (due to this problem, confirmed by a heap dump showing that the FJ workers are the leakers)? Because I've deployed to Tomcat for 7 years, and this issue won't be a problem AFAIK (since the threads will shut down and drop the references to the CL)