Hello all, I have an actor (call it myActor) which uses Akka I/O's Tcp system to create and listen to a connection. I.e. it does the Tcp.Connect, and Tcp.Register dance. The issue that I'm having is that when this actor dies, it's parent restarts it, which does a fresh Tcp.Connect, Tcp.Register dance. This is what I expect should happen. The issue is that when the myActor is restarted (for instance, due to an exception in the code), the Tcp actor that holds the socket is not aware of the restart. As a consequence I end up with socket leakage, and the new restarted copy of myActor has now created it's new Tcp.Connect/Tcp.Register dance.
What is the correct pattern to use here? Thanks, Daniel -- >>>>>>>>>> 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.
