#2479
  • Created on
    2012-09-06 21:00
  • Reported by
    viktorklang
  • Status
    New
  • Priority
    Normal (3)
  • Assigned to
    -
  • Milestone
    Backlog
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

THOUGHTSTORMING: Investigate possibility of quick clean shutdown of threads after ActorSystem.shutdown completes.

Might have to loop over dispatchers and terminate them
User picture
  on 2012-09-18 11:03 *
By viktorklang
Milestone changed from Mingus to Thoughtstorming
User picture
  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.
User picture
  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.
User picture
  on 2012-10-27 00:28 *
By viktorklang
Milestone changed from Thoughtstorming to Backlog
Updating tickets (#503, #1602, #1994, #2060, #2465, #2479)
User picture
  on 2012-11-02 12: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
User picture
  on 2012-11-02 13: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)