Just wondering, is there a way to limit the number of threads used by Dispatch in vers

Limiting threads about reboot HOT 3 CLOSED

dispatch commented on July 18, 2024

Limiting threads

from reboot.

Comments (3)

lloydmeta commented on July 18, 2024

Just confirmed that by switching back to non-Dispatch HTTP requests via Jsoup directly (which blocks), no errors occur.

from reboot.

n8han commented on July 18, 2024

You could block on the futures returned by Dispatch if that's the behavior you want.

Feel free to bring it up on the list, https://groups.google.com/forum/#!forum/dispatch-scala

from reboot.

lloydmeta commented on July 18, 2024

True, but blocking is not something I really want to do, especially since I'm using Dispatch from an actor.

In any case, I ended up doing this, which seemed to have worked:

// Http client
  lazy val followRedirects = true
  lazy val connectionPooling = true
  lazy val httpExecutorService: ExecutorService = Executors.newFixedThreadPool(httpExecutorThreads)
  lazy val config = new AsyncHttpClientConfig.Builder()
    .setExecutorService(httpExecutorService)
    .setMaximumConnectionsPerHost(maxConnectionsPerHost)
    .setAllowPoolingConnection(connectionPooling)
    .setAllowSslConnectionPool(connectionPooling)
    .setConnectionTimeoutInMs(connectionTimeoutInMs)
    .setRequestTimeoutInMs(requestTimeoutInMs)
    .setCompressionEnabled(compressionEnabled)
    .setFollowRedirects(followRedirects).build
  lazy val asyncHttpClient = new AsyncHttpClient(config)
  lazy val httpClient = new Http(asyncHttpClient)

  override def postStop() {
    httpClient.shutdown()
    httpExecutorService.shutdown()
  }