Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 20:47
    IgorFedchenko commented #4085
  • 20:46
    IgorFedchenko commented #4085
  • 15:09
    IgorFedchenko commented #4085
  • 11:24
    Kenji-Tanaka commented #3887
  • 10:45
    nagytech edited #4086
  • 10:45
    nagytech synchronize #4086
  • 10:43
    nagytech opened #4086
  • 09:00
    Horusiath commented #4077
  • 06:31
    Aaronontheweb commented #4085
  • 06:28
    Aaronontheweb commented #4085
  • 06:24
    Aaronontheweb commented #4085
  • Dec 07 11:49
    IgorFedchenko commented #4085
  • Dec 07 10:31
    IgorFedchenko commented #4085
  • Dec 07 08:36
    IgorFedchenko commented #4085
  • Dec 06 20:57
    IgorFedchenko commented #4085
  • Dec 06 20:32
    IgorFedchenko commented #4085
  • Dec 06 20:01
    IgorFedchenko commented #4085
  • Dec 06 19:55
    IgorFedchenko commented #4085
  • Dec 06 16:22
    Aaronontheweb labeled #3997
  • Dec 06 16:22
    Aaronontheweb closed #3997
Pawel Kasperek
@silentnull
@Horusiath Thank you for answer, that I'm starting learning Akka in F# :) . Maybe I will convert some plugins to F#, because sometimes is difficault use OO in FP.
Zetanova
@Zetanova
Yes, debugging is a horror in akka.net
Arjen Smits
@Danthar
Hallmark of async applications
Although with Akka its alot easier to test and debug your Actors in isolation.
John Nicholas
@MrTortoise
is there a way to get a timestamp on logging by default?
Roger Johansson
@rogeralsing
@MrTortoise There is a timestamp on logging already, is there something specific you mean?
Hussein Ait-Lahcen
@hussein-aitlahcen
@Horusiath Is there a way to ensure that a specified actor get executed in the same thread update after update ?
John Nicholas
@MrTortoise
@rogeralsing there is sorry, i meant much higher resolution ... seconds is a bit course grained.
Bartosz Sypytkowski
@Horusiath
@hussein-aitlahcen depending on your needs, you may define actor props with non-default dispatchers. Pinned one will give your actor while separate thread, synchornized one will use UI thread to execute you actor. Alternativelly you could use fork-join dispatcher two define separate thread pool for an actor (which could consist of 1 thread too)
John Nicholas
@MrTortoise
@hussein-aitlahcen http://getakka.net/docs/Dispatchers ... also here has an example of what you asked for https://github.com/petabridge/akka-bootcamp/tree/master/src/Unit-2
Jared Lobberecht
@Jared314
is there a way to have multiple hocon sections in the web.config with inheritance?
Roger Johansson
@rogeralsing
@MrTortoise ah, yes, I have a PR for that to support this akkadotnet/akka.net#1367
I need to add some tests for it to be merged first
but that will allow you to change how the logging templates are presented
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 ?