look at this profiler output showing the incoming references to a ClusterRouterGroup for a terminated Actor.... why are these still here? These ClusterRouterGroup (and settings) just keep piling up after the actor is terminated and recreated later
https://github.com/bitsofinfo/akka-debugging/tree/master/20170519a-question On Wednesday, May 17, 2017 at 8:11:01 PM UTC-6, bitsof...@gmail.com wrote: > > Whats the best way to properly terminate a ClusterRouterGroup actor > > i'm doing > > ActorRef actorRef = getContext().actorOf(new ClusterRouterGroup(new > RandomGroup(myPaths), > new > ClusterRouterGroupSettings(config.getClusterRouterGroup_totalInstances(), > myPaths, true, "xyz")).props(), actorPathName); > > Then later > > actorRef.tell(PoisonPill.getInstance(), ActorRef.noSender()); > > I see the Actor is stopped OK, then later my code then re-creates this > ClusterRouterGroup at a later point > > .... but what I'm noticing in a heap profiler is that the > ClusterRouterGroup and ClusterRouterGroupSettings settings are never being > garbage collected leading to a leak in my app. > > Thoughts? > -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
