you're creating another top-level actor
not sure if that's intentional or not
hah, thanks for noticing that, dunno if it's related to my issue
could you post a bigger gist?
is there a problem with using PatternMatch in Receive?
@rogeralsing I've pushed #1408 for initial Akka.Cluster.Tools, but when working on example program, I've found two serialization issuess: 1) is concerning JSON.NET not being able to deserialize IDictionary<Address, ...> (if get serialized as map of string keys) and 2) is about Wire having problems with finding default constructor for
System.Collections.Immutable.ImmutableDictionary
any of them is effectively blocking distributed pub/sub (and cluster client) examples to work
I wonder if there's something racy with the way routers create children
might be totally harmless
but we should investigate
?
nothing gets to Receive until after i see a zillion of those messages
see if those come in?
because I have literally never seen this message in two years of using Akka.NET
yeah, they still show up
can't give you any meaningful help with just what's in gitter
the interesting question is how that's even possible - these should all be self-contained
my gut tells me that the way you've exposed these actors inside your application contains shared mutable state
but without seeing that
I'm just guessing
if these are just child actors to some other actor then 100% of that state is private and self-contained
the router is shared amongst persistent actors created by a parent coordinator
none of this was happening until i converted the routed actors from ReceiveActor to ActorBase
return Akka.Actor.Props.Create(() => new Account(id, OtherRouter, ContactVerifier));
like that
thats how the router gets used, it only receives messages from siblings
why that instead of
ReceiveActor?