no, I use default mailboxes. First actor (ActorA) sends message to second actor (ActorB), and ActorB every 10 sec sends message to itself. Message ActorB -> ActorB is received in time, but message ActorA->ActorB can be received after long time
That makes sense. What are the purposes of these actors? what determines whether ActorB sends messages to itself? Also, are you running this in a docker container? What other processes are running on the machine that run this actor?
No, I didn't use Docker. ActorB sends message to itself to check current status of fixture every 10 sec. Nothing any processes except antivirus
ActorB is "check-alive" actor. ActorA notifies ActorB about states of fixture. ActorB checks how long fixture in disconnect/errored state every 10 sec. If fixture in errored/disconnected state after 3 times actorB notifies about it
Every successfull update to ActorA notifies ActorB to reset counter of error
Ok, isz this a commercial or pensource project? Is code available as I wonder whether this is the best way of doing things? I'm happy to take this off-line if that helps.Ok, ping me and let's have a chat in the new year. I'm a freelance .net developer with a lot of experience with actor systems.