Hi Brian, Akka remoting tries to maintain connectivity between remote systems -- it does not know about the concept of client and server, ActorRefs are globally addressable and therefore look completely symmetric. So if the client goes away, it tries to reconnect (how long and how often is configurable).
One way is to enable retry-gate on the server system so it does not try to reconnect and deliver buffered data to the system that has been gone (this is how it works now in 2.3 by default) but drops the buffer and reconnects only if there is actual new traffic (which is not in the buffer) trying to flow from the server to the other host. You can also use remote deatchwatch since it will signal Terminated for the clients that are gone, and will not attempt to connect to them. Unfortunately the quarantined client actor systems needs to be restarted to be able to connect again in this case. For pure client-server architectures akka.io or spray is recommended, for p2p like communication cluster is preferred. Remoting is very specialized and its most important feature is to be the foundation for clustering. That said, you can still use it for client-server setups, but there are caveats. -Endre On Thu, Jan 23, 2014 at 12:34 PM, Brian Fowler <[email protected]>wrote: > > Hi, > > We have recently moved from Akka 2.1.4 to Akka 2.2.3. We have actorSystems > that are essentially just clients with default host "127.0.0.1" and auto > assigned port connecting to actorSystems that are on remote boxes bound to > external ip addresses. The client and server system systems comunicate fine > (i.e. ask requests to actor refs - well actually typedActors) for a while > but then the client starts to not get responses from the server systems > any more and we get errors in the server log of the form > > > [2014-01-23 08:39:14,198] [ERROR] > [DataAugmentation-akka.actor.default-dispatcher-251] > akka.remote.EndpointWriter - AssociationError [ > akka.tcp://DataAugmentation@xxx:2552] -> [ > akka.tcp://[email protected]:33729]: Error [Association failed with [ > akka.tcp://[email protected]:33729]] [ > akka.remote.EndpointAssociationException: Association failed with [ > akka.tcp://[email protected]:33729] > Caused by: > akka.remote.transport.netty.NettyTransport$$anonfun$associate$1$$anon$2: > Connection refused: /127.0.0.1:33729 > > > This behaviour didn't occur under 2.1.4, has anyone else seen this. Know > how to fix it? > > Thanks, > > Brian > > > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: http://akka.io/faq/ > >>>>>>>>>> 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/groups/opt_out. > -- Akka Team Typesafe - The software stack for applications that scale Blog: letitcrash.com Twitter: @akkateam -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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/groups/opt_out.
