let me check that
under other top level actors
:D
key thing is that your actor path needs to be right in the config, so double check that first
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
yes!
that's the point!
I created some actors using the async behaviour
s/them/the messages
the Executors is a pool of actors routed by the monitor
ok
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
just checking
yes, I configured that
kkkkkkkkkkkkk
is there another one here?
are you using ReceiveActor?
I will write one example here, just a moment
the default behavior is Suspend already
in 1.0.1