Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 21:12
    Aaronontheweb commented #4001
  • 21:11

    Aaronontheweb on dev

    Added missing Persistence Testiā€¦ (compare)

  • 21:11
    Aaronontheweb closed #4001
  • 20:59
    sean-gilliam commented #3889
  • 20:59
    sean-gilliam opened #4001
  • 16:07
    spankr commented #3921
  • 15:55
    Aaronontheweb labeled #3765
  • 15:54
    Aaronontheweb labeled #3765
  • 15:54
    Aaronontheweb milestoned #3765
  • 15:53
    Aaronontheweb closed #3902
  • 15:23
    Aaronontheweb commented #3921
  • 15:11
    spankr commented #3921
  • 15:05
    Aaronontheweb commented #3973
  • 15:05
    Aaronontheweb commented #3973
  • 15:02
    Aaronontheweb commented #4000
  • 15:02
    Aaronontheweb milestoned #4000
  • 15:02
    Aaronontheweb assigned #4000
  • 15:01
    Aaronontheweb commented #3889
  • 14:55
    sean-gilliam commented #3889
  • 14:35
    IgorFedchenko commented #3973
Aaron Stannard
@Aaronontheweb
without seeing what's actually happening, i.e. the larger context
difficult to tell
never seen that error get logged before
Context.System.ActorOf is weird though - you're not creating a child when you do that
you're creating another top-level actor
not sure if that's intentional or not
Christian Duhard
@cduhard
shit, no it's not
hah, thanks for noticing that, dunno if it's related to my issue
Aaron Stannard
@Aaronontheweb
yeah me neither
could you post a bigger gist?
Christian Duhard
@cduhard
the weird thing is i have another pool created the exact same way that doesn't throw those errors
Christian Duhard
@cduhard
the only thing i've changed is i went from a ReceiveActor to ActorBase, it's likely something i missed there
Christian Duhard
@cduhard
i don't know what i'd put in the gist, what would help?
is there a problem with using PatternMatch in Receive?
Bartosz Sypytkowski
@Horusiath
@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
Christian Duhard
@cduhard
I am getting all these:
[Debug] Resolve of path sequence [/"user/contact-pool-e4338572-5484-4e67-94d5-59e7289d207e/$b"] failed
before the router even receives any messages.
Aaron Stannard
@Aaronontheweb
hmmm... mind creating an issue for that @cduhard ?
I wonder if there's something racy with the way routers create children
might be totally harmless
but we should investigate
Christian Duhard
@cduhard
could it have anything to do with monitoring?
Aaron Stannard
@Aaronontheweb
using Akka.Monitoring?
Christian Duhard
@cduhard
yes
Aaron Stannard
@Aaronontheweb
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
return Akka.Actor.Props.Create(() => new Account(id, OtherRouter, ContactVerifier));
like that
thats how the router gets used, it only receives messages from siblings