Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 12 15:42
    Aaronontheweb synchronize #4086
  • Dec 12 15:42
    Aaronontheweb closed #4083
  • Dec 12 15:42

    Aaronontheweb on dev

    Fix #4083 - Endpoint receive bu… (compare)

  • Dec 12 15:42
    Aaronontheweb closed #4089
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb opened #4093
  • Dec 12 14:20
    Aaronontheweb commented #4092
  • Dec 12 14:14
    Aaronontheweb labeled #4089
  • Dec 12 14:14
    Aaronontheweb labeled #4089
  • Dec 12 14:11
    Aaronontheweb synchronize #4089
  • Dec 12 14:10
    Aaronontheweb synchronize #4086
  • Dec 12 14:09

    Aaronontheweb on dev

    Convert to ImmutableHashSet for… (compare)

  • Dec 12 14:09
    Aaronontheweb closed #4090
  • Dec 12 12:04
    nagytech synchronize #4092
  • Dec 12 11:53
    nagytech synchronize #4092
  • Dec 12 11:49
    nagytech edited #4092
  • Dec 12 11:40
    nagytech opened #4092
  • Dec 12 11:32
    nagytech edited #4091
Daniel Ferreira Monteiro Alves
@danfma
:smile:
Aaron Stannard
@Aaronontheweb
what's shakin
Daniel Ferreira Monteiro Alves
@danfma
hey guys, do you know if there is any problem with the routers and the config at the app.config?
Andrew Skotzko
@skotzko
@danfma can you be more specific? what’s happening?
Daniel Ferreira Monteiro Alves
@danfma
sorry, I am slow here! :D
I created an actor as a router (round-robin) in the config
then I tried to create that actor inside another one
 _executors = Context.ActorOf(
                Props.Create(() => new JobExecutor(_application))
                    .WithRouter(FromConfig.Instance),
                "Executors");
Aaron Stannard
@Aaronontheweb
what's the config look like?
Daniel Ferreira Monteiro Alves
@danfma
but I always got a strange error, something saying that the actor has already being configured
just the same as the example from the site
Aaron Stannard
@Aaronontheweb
which one?
Daniel Ferreira Monteiro Alves
@danfma
akka.actor.deployment {
  /Executors {
    router = round-robin-pool
    nr-of-instances = 5
  }
}
Aaron Stannard
@Aaronontheweb
ah, I see what your issue is - you want to re-use that router configuration in multiple places
right?
Daniel Ferreira Monteiro Alves
@danfma
no, I just wanted to define the router at config and not at code
the exception is
`

An exception of type 'Akka.Configuration.ConfigurationException' occurred in Akka.dll but was not handled in user code

Additional information: Configuration problem while creating [akka://BeedroneProcessor/user/Monitor/Executors] with router dispatcher [akka.actor.default-dispatcher] and mailbox and routee dispatcher [akka.actor.default-dispatcher] and mailbox [].

`
Andrew Skotzko
@skotzko
I think your actor path is wrong
your router is not a top level actor in this case
Daniel Ferreira Monteiro Alves
@danfma
user/Executors?
Andrew Skotzko
@skotzko
/Monitor/Executors in the config
Daniel Ferreira Monteiro Alves
@danfma
ops
let me check that
Andrew Skotzko
@skotzko
or /*/Executors to reuse it
under other top level actors
Daniel Ferreira Monteiro Alves
@danfma
You are right! I was dumb here! I forgot that actor is a child of another one!
:D
Andrew Skotzko
@skotzko
no worries :)
key thing is that your actor path needs to be right in the config, so double check that first
Daniel Ferreira Monteiro Alves
@danfma
ok
another question, let me say that I want to create some kind of processors on demand
I created a service with a queue of messages
the actors should pop some messages from time to time
Joshua Benjamin
@annymsMthd
Maybe a pooled router with a resizer?
Daniel Ferreira Monteiro Alves
@danfma
I was thinking in use the router to create that behaviour, while checking from time to time that queue
yes!
that's the point!
I created some actors using the async behaviour
Andrew Skotzko
@skotzko
i guess you could have one actor scheduled to receive messages off the queue and then hand them to a resizable pool router for scalable processing
s/them/the messages
Daniel Ferreira Monteiro Alves
@danfma
that's what the monitor is doing the previous code
the Executors is a pool of actors routed by the monitor
Andrew Skotzko
@skotzko
ah
ok
Daniel Ferreira Monteiro Alves
@danfma
one thing is funny
if I use the async from the .NET then the actors does not respect the default behaviour that only one message is processed by an actor at a time, apparenly
apparently*
is the the right thing when using async or a problem
Roger Johansson
@rogeralsing
What version are you using?