hmmm.... could be - calling it from the child actor/
?
Christian Duhard
@cduhard
yes
Aaron Stannard
@Aaronontheweb
only way I could see that happening would be if the actor was receiving a message while it was still being created... which Akka.Monitoring implementation are you using?
Christian Duhard
@cduhard
statsd
nothing gets to Receive until after i see a zillion of those messages
Aaron Stannard
@Aaronontheweb
could you do a test for me and try commenting the monitoring method calls out
see if those come in?
because I have literally never seen this message in two years of using Akka.NET
Christian Duhard
@cduhard
yeah i'm about to do that
yeah, they still show up
Aaron Stannard
@Aaronontheweb
post a gist with the full source for this
can't give you any meaningful help with just what's in gitter
Christian Duhard
@cduhard
i understand
Aaron Stannard
@Aaronontheweb
basically it's a race condition of some sort - someone's trying to resolve a reference to a child actor that doesn't exist yet
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
_
Christian Duhard
@cduhard
the actors that use this router are PersistenActors
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