Hi Patrik, it has been a while but I want to tell you that it was an error of mine. Long story short: I had an unwanted situation of 2 actor systems instead of one. Sending a message to actorRef of system1 to actorRef of system2 worked. Switching to actorSelection (as in AtLeastOnceDelivery) did not (of course). Thank you for your interest.
giampaolo Il giorno venerdì 22 maggio 2015 16:22:38 UTC+2, Patrik Nordwall ha scritto: > > Hi giampaolo, > > Sorry for the delay. This question must have fallen between the cracks. > > I hope you have found the problem. This should absolutely work. Let me > know otherwise and I will investigate. > > Regards, > Patrik > > On Mon, May 11, 2015 at 3:21 PM, Giampaolo <giampaolo...@gmail.com > <javascript:>> wrote: > >> Hi to all, >> >> I'm quite new to Akka and this is my first post on the mailing list. I >> have an Actor System where I have a sharding region. Till now, I sent >> messages to actors behind region in a way like this: >> >> region ! MyActor.Message(param1, param2, to) >> >> Region is an ActorRef I get with val region = >> ClusterSharding(AkkaInitializer.system.get).shardRegion(MyActor.shardName) >> >> MyActor is a companion object for MyActor actor which is under sharding. The >> to parameter allows to correctly reach the right actor. >> >> This works like a charm (and I really thank Akka developer for providing a >> so powerful tool to solve complex problems). >> >> >> >> Now I want to ensure that my Message is delivered at least once, so I >> changed the code like this (adding also the AtLeastOnceDelivery trait): >> >> >> deliver(region.path, deliveryId => MyActor.Message(param1, param2, to, >> deliveryId)) >> >> >> This does not work as expected. Unfortunately I get a dead letter for every >> time a delivery is tried. This surprises me since I thought that since >> region variable normally works, also using its path should work. Probably >> I'm missing some detail about sharding internals or I'm confusing >> ActorRef/Path definitions. I thought that while having a path does not >> implies to have an incarnated actor, the opposite was true. >> >> >> Could someone explain me where I am wrong? Thank you in advance for your >> time. >> >> >> giampaolo >> >> >> >> -- >> >>>>>>>>>> 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 <javascript:>. >> To post to this group, send email to akka...@googlegroups.com >> <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 > > -- >>>>>>>>>> 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+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
