anyone know how to send to a clustered consistent-hashing-pool created on another port/process? Tried doing an actorselection & tell but it doesn't get there (deadlettered). tried creating the router on the secondary client but then it's a diff actor that receives the message. not sure if i'm trying to do something i shouldn't or just missing something simple
@rogeralsing, looking good for local serialization tests. I gave it a run through a bunch of experiements in F# and didn't have any hitches. I did notice that I could not serialize a C# Action, though (whether or not you want to support that is another question)
If you share your akka branch I will try with some more complicated/remote experiments. I had noticed with some of the other serializers that what worked fine in-process would fail across processes/remotely
For Action, I saw the much-loathed VerificationException
@hhko, no that is not a bug, there is simply no way to observe if there are actors processing messages. lets say you have 1 mil actors, there is simply no way to synchronize that amount of work. when you think the last one is done, the first one might have started to process again.
Hello People - just wrapping my head around persistence - if I implement AtLeastOnceDeliveryActor, would I need to use a Stash as well? (I can't lose any messages and I can't assume the same host will be available).
Hi, n00b question. If I want to send a message to an actor that is physically on the same machine, but hosted in a different process, can I just use an ActorSelection referencing for instance akka://mysystem/user/Foo, or do i need to use a remote actor ref?
@irperez@rogeralsing I did not set out to use Akka.Remote, or TCP, specifically. I wanted to do a little POC where I host an actor in a Windows service, and then have a console app (running on the same machine, but separate process) send a message into the actor system hosted on the server.