Knowledge Base

Showing results for 
Search instead for 
Did you mean: 

How to resolve "thread pool task queue is full" error


Our logs are showing the following error message which says that the thread pool task queue is full. We restarted the Controller and the problem went away. Is this normal, and should we increase our thread pool as a result?


[#|2017-01-07T04:52:34.017-0500|SEVERE|glassfish3.1.2|grizzly|_ThreadID=34;_ThreadName=Thread-5;|doSelect exception 
java.util.concurrent.RejectedExecutionException: The thread pool's task queue is full, limit: 4096
at com.sun.grizzly.util.AbstractThreadPool.onTaskQueueOverflow(
at com.sun.grizzly.util.SyncThreadPool.execute(
at com.sun.grizzly.util.GrizzlyExecutorService.execute(
at com.sun.grizzly.http.StatsThreadPool.execute(
at com.sun.grizzly.NIOContext.execute(
at com.sun.grizzly.NIOContext.execute(
at com.sun.grizzly.SelectorHandlerRunner.handleSelectedKey(
at com.sun.grizzly.SelectorHandlerRunner.handleSelectedKeys(





As of version 4.2.x, for large profiles, our team recommends 24 CPU Cores. This machine only had 8 Cores.

To resolve this, first backup the existing domain.xml configuration file.


Then make the following changes to the domain.xml file:


<thread-pool max-thread-pool-size="32" name="http-thread-pool" min-thread-pool-size="16"></thread-pool>

Change to:
<thread-pool max-thread-pool-size="64" name="http-thread-pool" min-thread-pool-size="64" max-queue-size="-1"></thread-pool>


And restart the App Server:

  1. cd <ControllerDir>/bin
  2. ./ stop-appserver
  3. ./ start-appserver   [This will take some time, depending on the size]


Version history
Revision #:
3 of 3
Last update:
‎06-15-2017 09:38 AM
Updated by:
Labels (1)
0 Kudos