Hi Diego, it seems it is an oversight that the dispatcher for at least the actor parts of the pool infrastructure cannot be configured anywhere. I created a ticket to track adding this feature:
https://github.com/akka/akka-http/issues/1278 Thanks, Johannes On Thursday, June 22, 2017 at 12:44:53 PM UTC+2, Diego Martinoia wrote: > > Hi there, > > I'm wondering how to set the dispatcher on which to run all the > akka-http-client operations. There doesn't seem to be any config voice for > it as far as I can tell. > > I have assigned a separate dispatcher at the materializer that I'm using > in the client, but I'm unsure if this is sufficient because the logs still > point to the default dispatcher threads. > > Is there something else that needs to be done? I have seen inside the > library that the PoolGateway might still be running on the def.disp. even > with the materializer one re-assigned. > > Thanks, > > D. > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
