Yes, it sounds like the same issue. The important point is the log message: 04:12:24.833 DEBUG Associated [akka.tcp://OurProgrammhostname.com:3552 <http://[email protected]:3552>] <- [akka.tcp://GatlingSystem@ gatlinghostname:9044]
The re-connect is going to be associated, but as the internal state of the EndpointManager becomes incosistent, an AssertionError will be thrown. As a workaround I wrote an Auto-Restarter which restarts an ActorSystem in case of unexpected shutdown. But the Netty-NIO stuff was not shutdown orderly. The TCP-Port was still bound and restarts fail. Finally I investigated a little bit more and found a few things I wouldn't do (maybe I have not enough insight): - the death of an EndpointManager should not kill the entire ActorSystem (why not restart this subsystem?) - as theEndpointManager is doing a lot of things, I would move the EndpointManager beyond an EndpointSupervisor who ensures aliveness - Resources (like TCP-Channels) should be closed (at least) automatically in postStop - the map to find quarantined UID's should be a 1 [Address] to N list and not 1:1 (have a look in akka.remote.EndpointManager.EndpointRegistry) -- >>>>>>>>>> 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.
