Hello,
Thank you for your help. After reading your comment ("the router, not for
it's routees") I remembered about actor groups (as opposed to pools).
I defined a common pinned dispatcher (in application.conf, directly under
"akka" element):
pinnedDispatcher {
type = "PinnedDispatch
I'm not experienced with configuring routers from config, since I prefer
using code, but as far as I understand you did set a dispatcher for the
/master/worker - the router, not for it's routees - the actual worker
actors. If you print the thread name in constructor an in receive of
workers you
Hello,
I tried to use PinnedDispatcher using the following configuration (in
application.conf):
app {
pinnedDispatcher {
type = "PinnedDispatcher"
executor = "thread-pool-executor"
thread-pool-executor.allow-core-timeout = off
thread-pool-executor {
Hi
A PinnedDispatcher may be what your looking for. It creates a dedicated
thread for each actor.
It's documented (with an example) here:
http://doc.akka.io/docs/akka/current/scala/dispatchers.html#types-of-dispatchers
Best Regards,
Rafał
--
>> Read the docs: http://akka.io/docs/
