Hi Randy,
without setting max-pool-size-max (which defaults to 64) you will not be able
to see more than 64 threads. May I ask why you want to create 100 threads for
handling a single stream of incoming connections? I would expect at least 99 of
them to be idle at all times. If you want to
Hi Roland,
Thanks for the response. The 100 threads was just to verify that I could
control the # threads. I didn’t realize it was using a bounded task queue.
How do I configure a dedicated dispatcher for the operations in the flows
that handle each connection as opposed to inheriting it
Hi Randy,
What makes you say it doesn't respect your core pool size?
--
Cheers,
√
On 16 Jan 2015 02:34, Randy Fox randy@connexity.com wrote:
I am trying to assign a dispatcher to be used for my http server (using
the new Akka HTTP Server) and can’t get it to honor my pool size settings.
I am trying to assign a dispatcher to be used for my http server (using the
new Akka HTTP Server) and can’t get it to honor my pool size settings.
Logs show it is using the dispatcher, but visualvm shows it is not using
the core pool size settings. Loos like it might be using the defaults
