Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 21:23
    Aaronontheweb commented #5604
  • 20:10

    Aaronontheweb on dev

    Trap all exception thrown while… (compare)

  • 20:10
    Aaronontheweb closed #5972
  • 20:10
    Aaronontheweb milestoned #5972
  • 20:10
    Aaronontheweb demilestoned #5972
  • 20:10
    Aaronontheweb milestoned #5972
  • 20:10
    Aaronontheweb labeled #5972
  • 20:09

    Aaronontheweb on v1.4

    Trap all exception thrown while… (compare)

  • 20:09
    Aaronontheweb closed #5971
  • 20:09
    Aaronontheweb auto_merge_disabled #5971
  • 19:47
    zbynek001 commented #5604
  • 19:06
    Aaronontheweb commented #5604
  • 19:03
    zbynek001 commented #5604
  • 17:14

    Arkatufus on 1.4.38-beta2

    (compare)

  • 17:12

    Arkatufus on master

    Bump AkkaVersion from 1.4.37 to… Bump MongoDB.Driver from 2.15.0… Fix Akka.Persistence.MongoDb co… and 4 more (compare)

  • 17:12
    Arkatufus closed #261
  • 17:06
    Arkatufus auto_merge_enabled #261
  • 17:05
    Arkatufus opened #261
  • 16:54
    Arkatufus opened #5972
  • 16:42
    Aaronontheweb auto_merge_enabled #5971
Daniel Ferreira Monteiro Alves
@danfma

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?
Daniel Ferreira Monteiro Alves
@danfma
the last one
just checking
Andrew Skotzko
@skotzko
default respects one message at at time
Roger Johansson
@rogeralsing
And what async behavior? Suspend or reentrant?
Natan Vivo
@nvivo
this async stuff must be a problem with Brazilians...
Andrew Skotzko
@skotzko
you have to specifically enable reentrant
Daniel Ferreira Monteiro Alves
@danfma
the version on nuget is the 1.0.0
yes, I configured that
kkkkkkkkkkkkk
is there another one here?
Natan Vivo
@nvivo
you should leave the default or specify Suspend
are you using ReceiveActor?
Daniel Ferreira Monteiro Alves
@danfma
yes
I will write one example here, just a moment
Natan Vivo
@nvivo
just do Receive<Foo>(async foo => { .. })
the default behavior is Suspend already