Patrik, there is no firewall between those machines. I understand that NAT is not supported and it is quite common for servers to have more than one interface. While NAT is problematic, being able to receive messages directed to different network interfaces by single Akka application is something rather expected. Otherwise it binds Akka deployments to low level network topography and makes complex setups much harder to implement and manage.
On Friday, June 13, 2014 8:05:16 AM UTC+2, Patrik Nordwall wrote: > > Hi, > > NAT setups are not supported as explained here: > http://doc.akka.io/docs/akka/2.3.3/general/remoting.html#Peer-to-Peer_vs__Client-Server > and the the hostname must be exactly the same as the configured > akka.remote.netty.tcp.hostname > > Does that explain your issue? > > /Patrik > > > On Wed, Jun 11, 2014 at 11:40 PM, Łukasz Kuczera <[email protected] > <javascript:>> wrote: > >> Hello hAkkers. >> I've strange problems with mentioned upgrade. Communication with remote >> actors work but only partially. There are two components that talk to each >> other via remoting. Here is excerpt from the logs. >> >> Portal: >> >> [INFO] [06/10/2014 19:46:42.312] >> [QLP-SCRIBE-CLIENT-akka.actor.default-dispatcher-4] >> [akka://QLP-SCRIBE-CLIENT/system/transports/akkaprotocolmanager.tcp0/akkaProtocol-tcp%3A%2F%2FQLP-SCRIBE-CLIENT%4010.68.177.228%3A44658-5] >> >> Message [akka.remote.transport.AssociationHandle$Disassociated] from >> Actor[akka://QLP-SCRIBE-CLIENT/deadLetters] to >> Actor[akka://QLP-SCRIBE-CLIENT/system/transports/akkaprotocolmanager.tcp0/akkaProtocol-tcp%3A%2F%2FQLP-SCRIBE-CLIENT%4010.68.177.228%3A44658-5#-1710053545] >> >> was not delivered. [8] dead letters encountered. This logging can be turned >> off or adjusted with configuration settings 'akka.log-dead-letters' and >> 'akka.log-dead-letters-during-shutdown'. >> [INFO] [06/10/2014 19:46:42.313] >> [QLP-SCRIBE-CLIENT-akka.actor.default-dispatcher-4] >> [akka://QLP-SCRIBE-CLIENT/system/transports/akkaprotocolmanager.tcp0/akkaProtocol-tcp%3A%2F%2FQLP-SCRIBE-CLIENT%4010.68.177.228%3A44658-5] >> >> Message >> [akka.remote.transport.ActorTransportAdapter$DisassociateUnderlying] from >> Actor[akka://QLP-SCRIBE-CLIENT/deadLetters] to >> Actor[akka://QLP-SCRIBE-CLIENT/system/transports/akkaprotocolmanager.tcp0/akkaProtocol-tcp%3A%2F%2FQLP-SCRIBE-CLIENT%4010.68.177.228%3A44658-5#-1710053545] >> >> was not delivered. [9] dead letters encountered. This logging can be turned >> off or adjusted with configuration settings 'akka.log-dead-letters' and >> 'akka.log-dead-letters-during-shutdown'. >> >> >> and here is database: >> >> [WARN] [06/10/2014 20:00:00.197] >> [new-scribe-system-akka.remote.default-remote-dispatcher-24] [akka.tcp:// >> [email protected]:5225/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FQLP-SCRIBE-CLIENT%4010.101.159.54%3A5225-1] >> >> Association with remote system [akka.tcp:// >> [email protected]:5225] has failed, address is now gated >> for [5000] ms. Reason is: [Disassociated]. >> >> What I figured out so far it seems that they try to communicate via local >> address. Not public. This is deployed on Amazon AWS, locally it works fine. >> What's also interesting is that some messages do work but some do not. I >> ran that locally with exact same data and it worked. >> >> Last but not least I'm not sure if that is a feature or a bug (for me it >> is a bug) but host name resolution doesn't work well with Akka remoting. If >> I have one node that is configured to listen on specific address A then if >> message arrive on another interface but on the same host it doesn't work. >> Even localhost vs. 127.0.0.1 fails with log message that it wasn't targeted >> to "me". >> >> Sorry for lengthy post. I hope someone can chime in and help. >> >> -- >> >>>>>>>>>> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > Patrik Nordwall > Typesafe <http://typesafe.com/> - Reactive apps on the JVM > Twitter: @patriknw > > <http://www.scaladays.org/> > > -- >>>>>>>>>> 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.
