Akka Messages Duplicated

[Joseph Mansigian]

I have an application that uses remote addressing exclusively.  The application is under development on one local machine; one actor system spanning several JVM. When I send a message the message always arrives at its intended recipient actor and is processed. Program output verifies that the affected actor has received and processed the message.  The program runs as expected; no messages are ever lost.

The thing that is mystifying me is that whenever I send a message a duplicate  of the message is also sent to the same actor using a local path instead of the correct remote path.  As you would expect the message cannot be delivered and it goes to the DeadLetter place.   I am monitoring the Event Bus and see this on a regular basis.  I have looked very scrupulously to see if I could be sending the message twice but cannot find this happening.  Also I don't even have any configuration ( application.conf ) that is capable of creating a local path to an actor.

Would be interested in two things:

1) Has anybody else seen this behavior.

2) Anyone have ideas about how I can research what is going on.

Software in use: 

    akka 2.4.16

    scala 2.11.8

    java  1.8.0_112

    linux  3.13.0-24-generic #47-Ubuntu SMP 

Thanks, Joe

    

[Patrik Nordwall]

That sounds very strange, and interesting. Do you have a way to reproduce it that you can share? Any interesting logging if you enable debug log level?

/Patrik

--
>>>>>>>>>> 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 akka-user+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[Joseph Mansigian]

Hello Patrik,

Thank you for your interest.  I never thought to configure debug on because I was consistently getting every output correct which could only happen if all of the messages got through.  However debug revealed the key.  What was happening is that, at the growing edge of the program - after it had sent all of the messages needed to show a correct output - I had an error that dumped the JVM.  Specifically it was a match error in the receive loop caused by their not being a match for the case class ( message ) coming through and no catch all default.  Fixing this corrected the problem.  I never thought to debug a program that consistently produced correct output.  Thank you.

Joe