Hi,
> The registration process executes successfully and I receive a response > back from the remote-registration-service. The registration-client-service > then shuts down. > > At this point, the remote-registration-service starts to print out dead > letter messages as shown below. I have marked the messages from the > remote-registration-service in *Bold* > These are internal messages, you should not be concerned about them. Dead letters are not harmful per se, they usually happen when an actor is stopped but someone still sends them a few messages -- they get delivered to dead letters. > > *[ERROR] [05/01/2014 19:33:19.998] > [remote-registration-service-akka.remote.default-remote-dispatcher-6] > [akka.tcp://[email protected]:8245/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2Fregistration-client-system0c0be54e-87d8-4920-8725-019b2e8ab0f0%40127.0.0.1%3A2552-0/endpointWriter > <http://[email protected]:8245/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2Fregistration-client-system0c0be54e-87d8-4920-8725-019b2e8ab0f0%40127.0.0.1%3A2552-0/endpointWriter>] > AssociationError [akka.tcp://[email protected]:8245 > <http://[email protected]:8245>] <- > [akka.tcp://registration-client-system0c0be54e-87d8-4920-8725-019b2e8ab0f0@127.0.0.1:2552 > <http://registration-client-system0c0be54e-87d8-4920-8725-019b2e8ab0f0@127.0.0.1:2552>]: > Error [Shut down address: > akka.tcp://registration-client-system0c0be54e-87d8-4920-8725-019b2e8ab0f0@127.0.0.1:2552 > <http://registration-client-system0c0be54e-87d8-4920-8725-019b2e8ab0f0@127.0.0.1:2552>] > [* > *akka.remote.ShutDownAssociation: Shut down address: > akka.tcp://registration-client-system0c0be54e-87d8-4920-8725-019b2e8ab0f0@127.0.0.1:2552 > <http://registration-client-system0c0be54e-87d8-4920-8725-019b2e8ab0f0@127.0.0.1:2552>* > *Caused by: akka.remote.transport.Transport$InvalidAssociationException: > The remote system terminated the association because it is shutting down.* > *]* > The above line means that the remote system has been shut down, and we cannot connect back ever to it. As a sidenote, be aware that akka-remoting is not a client-server architecture (see http://doc.akka.io/docs/akka/2.3.2/general/remoting.html#Peer-to-Peer_vs__Client-Server) but a peer-to-peer architecture, so any side might open a connection. At this point, the registration-client-system-{UUID} begins its shutdown > process. Then, I see a very interesting error message from the > remote-registration-service which seems to indicate that the > remote-registration-service is aware of the registration-client-system, but > is for some reason not sending any messages back to it! > Yes, it looks like it was connected before. You can get more information by elevating the logging levels in remoting ( http://doc.akka.io/docs/akka/2.3.2/general/configuration.html#akka-remote), you can use akka.remote.log-sent-messages, akka.remote.log-received-messages to see what messages are sent and received. It can be that your timeout is just too small, I recommend trying the resolution several times before giving up. Also, instead of using a Future and Await you should use ordinary message sends for identification: http://doc.akka.io/docs/akka/2.3.2/scala/actors.html#Identifying_Actors_via_Actor_Selection And you should upgrade to Akka 2.3.2 :) -Endre > > > Thanks, > > Siddhu > > On Saturday, 2 March 2013 14:21:50 UTC, rkuhn wrote: > >> Hi Daniel, >> >> 1 mar 2013 kl. 14:32 skrev Daniel Krzywicki: >> >> Hi, >> >> I want to write a simple client-server app using akka: >> >> - a server actor awaits for requests in a first actor system >> - a new actor system is created, along with a client actor, which >> submits a task remotedly to the server actor >> - the server actor computes some result and sends it back to the >> client actor >> - the client actor processess the results, then shuts down its actor >> system. >> >> >> The server actor does not retain references to the client. However, when >> the client system shuts down, the server starts throwing akka.remote. >> EndpointException. >> >> >> Thanks for trying out 2.2-M1! The new remoting maps the connection life >> cycle to an actor’s life cycle, and that actor then “fails” when the >> connection is closed. We have a ticket in the pipeline (#2824 - Change >> logging of actor failures) to enable different logging strategies for >> actors according to the application’s needs, and we will apply this to >> sanitize the overly verbose logging of the remoting layer. >> >> Until then please just ignore these exceptions, they are expected when >> the client disconnects. >> >> I’m assuming that afterwards remoting still works, right? If not, then >> please give more information (confirm the Akka version used and include >> full stack traces). >> >> Regards, >> >> Roland >> >> >> How to gracefully disconnect these systems so that the client one can >> shutdown without the server one bothering? >> >> Best regards >> >> -- >> >>>>>>>>>> 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?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> >> >> *Dr. Roland Kuhn* >> *Akka Tech Lead* >> Typesafe <http://typesafe.com/> – Empowering professional developers to >> build amazing apps. >> twitter: @rolandkuhn <http://twitter.com/#!/rolandkuhn> >> >> -- > >>>>>>>>>> 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. > -- 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://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.
