Re: [akka-user] Path to Actor changed by Akka

2017-04-15 Thread Patrik Nordwall
You are welcome lör 15 apr. 2017 kl. 20:28 skrev Joseph Mansigian < joseph.c.mansig...@gmail.com>: > You were correct in your suspicion that the destination actor was not > running at the given path. In fact it was not running at all. In > debugging I was thrown off by seeing that a print of

Re: [akka-user] Path to Actor changed by Akka

2017-04-15 Thread Joseph Mansigian
You were correct in your suspicion that the destination actor was not running at the given path. In fact it was not running at all. In debugging I was thrown off by seeing that a print of 'self.path' in the destination actor expressed a local path and I had configured a remote path to the

Re: [akka-user] Path to Actor changed by Akka

2017-04-15 Thread Patrik Nordwall
The problem is not some wrong translation. Are you sure that the destination actor is running at the given path? You can enable more logging: http://doc.akka.io/docs/akka/2.5/scala/logging.html#Auxiliary_remote_logging_options /Patrik fre 14 apr. 2017 kl. 15:06 skrev Joseph Mansigian <

[akka-user] Path to Actor changed by Akka

2017-04-14 Thread Joseph Mansigian
When sending a message to a remote actor I get an always repeatable failed send with a dead letter being produced. The recipient actor is a remote actor in a different JVM than the sending actor but both sender and recipient are executing on the same machine. Both sender and recipient