Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 14:14
    Aaronontheweb labeled #4089
  • 14:14
    Aaronontheweb labeled #4089
  • 14:11
    Aaronontheweb synchronize #4089
  • 14:10
    Aaronontheweb synchronize #4086
  • 14:09

    Aaronontheweb on dev

    Convert to ImmutableHashSet for… (compare)

  • 14:09
    Aaronontheweb closed #4090
  • 12:04
    nagytech synchronize #4092
  • 11:53
    nagytech synchronize #4092
  • 11:49
    nagytech edited #4092
  • 11:40
    nagytech opened #4092
  • 11:32
    nagytech edited #4091
  • 11:32
    nagytech opened #4091
  • 10:13
    nagytech commented #3954
  • 05:29
    nagytech commented #4090
  • 05:29
    nagytech opened #4090
  • Dec 11 23:52
    scptre commented #4082
  • Dec 11 14:26
    nagytech commented #3954
  • Dec 11 11:18
    nagytech edited #4089
  • Dec 11 11:17
    nagytech opened #4089
  • Dec 11 11:00
    nagytech commented #4083
John Nicholas
@MrTortoise
oh cool thats what i want ;) thanks ill keep an eye on that then, thats cleaner than what i'm doing
Hussein Ait-Lahcen
@hussein-aitlahcen
@Horusiath Thanks, the fork join dispatcher seems to fit
Diego Frata
@diegofrata

I'm creating a ReceivePersistentActor using Context.DI().Props<T>() and I'm getting this exception:
```
Exception thrown: 'System.NotSupportedException' in Akka.dll

Additional information: DequeBasedMailbox required, got: UnboundedMailbox

An (unbounded) deque-based mailbox can be configured as follows:

my-custom-mailbox {

    mailbox-type = "Akka.Dispatch.UnboundedDequeBasedMailbox"

}
I shouldn't need to specify my own Mailbox type, right? It seems like a bug to me.
Diego Frata
@diegofrata
My actors implement a common interface and I was using the interface as T instead of the concrete type. It was messing the ActorCell creation. I wouldn't say this is a bug, but it's definitely a point for improvement IMHO. In the meantime I'm passing concrete types.
Thomas Tomanek
@thomastomanek
hmm, there was a bug ages ago that returned a similar/same exception when using autofac to create actors
#941
Christian Duhard
@cduhard
Christian Duhard
@cduhard

what might these messages mean?

[Debug] Resolve of path sequence [/"user/contact-pool-e4338572-5484-4e67-94d5-59e7289d207e/$b"] failed

Aaron Stannard
@Aaronontheweb
@cduhard what were you trying to do?
Christian Duhard
@cduhard
not sure when that log message is getting fired, but I have a small RR pool per Parent that gets handed to it's children
Aaron Stannard
@Aaronontheweb
that message occurs when an actor selection fails
the requested path could not be found
Christian Duhard
@cduhard
                Context.System.ActorOf(
                    Akka.Actor.Props.Create<ContactVerificationActor>(ContactService.GetInstance(),
                        new SequenceService())
                        .WithRouter(new RoundRobinPool(2))
                    , "contact-pool-{0}".FormatWith(Guid.NewGuid()));
why would selection fail? i have never seen that message before today
Aaron Stannard
@Aaronontheweb
my bad - here's where it gets called
private IActorRef ResolveActorRef(IInternalActorRef actorRef, IReadOnlyCollection<string> pathElements)
        {
            if(pathElements.Count == 0)
            {
                _log.Debug("Resolve of empty path sequence fails (per definition)");
                return _deadLetters;
            }
            var child = actorRef.GetChild(pathElements);
            if(child.IsNobody())
            {
                _log.Debug("Resolve of path sequence [/{0}] failed", ActorPath.FormatPathElements(pathElements));
                return new EmptyLocalActorRef(_system.Provider, actorRef.Path / pathElements, _eventStream);
            }
            return child;
        }
Inside LocalActorRefProvider
Christian Duhard
@cduhard
the messages eventually stop and everything seems to move along fine
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?