java.util.concurrent.RejectedExecutionException: The thread pool's task queue is full, limit: 4096

Stack Overflow | Tom | 3 months ago
  1. 0

    Glassfish: The thread pool's task queue is full

    Stack Overflow | 3 months ago | Tom
    java.util.concurrent.RejectedExecutionException: The thread pool's task queue is full, limit: 4096
  2. 0

    Periodical error on Glassfish after a small load and running for a few hours. No one is connected to the server anymore and the error appear a few hours after a stress test. The questions are : * how is it possible that the such an error appear when there is no more load ? * since no requests are made, what is filling the pool ? * can we see which request fill in the pool ? can we activate any logs ? Thanks. The error : {noformat} [#|2012-02-02T19:43:24.375+0100|SEVERE|glassfish3.1.1|grizzly|_ThreadID=119;_ThreadName=Thread-2;|doSelect exception java.util.concurrent.RejectedExecutionException: The thread pool's task queue is full, limit: 4096 at com.sun.grizzly.util.AbstractThreadPool.onTaskQueueOverflow(AbstractThreadPool.java:473) at com.sun.grizzly.util.QueueLimitedThreadPool.onTaskQueueOverflow(QueueLimitedThreadPool.java:97) at com.sun.grizzly.util.QueueLimitedThreadPool.execute(QueueLimitedThreadPool.java:88) at com.sun.grizzly.util.GrizzlyExecutorService.execute(GrizzlyExecutorService.java:162) at com.sun.grizzly.http.StatsThreadPool.execute(StatsThreadPool.java:127) at com.sun.grizzly.NIOContext.execute(NIOContext.java:510) at com.sun.grizzly.NIOContext.execute(NIOContext.java:488) at com.sun.grizzly.SelectorHandlerRunner.handleSelectedKey(SelectorHandlerRunner.java:370) at com.sun.grizzly.SelectorHandlerRunner.handleSelectedKeys(SelectorHandlerRunner.java:263) at com.sun.grizzly.SelectorHandlerRunner.doSelect(SelectorHandlerRunner.java:200) at com.sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java:132) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) |#] {noformat} Glassfish connector config : [#|2012-02-02T19:43:26.844+0100|INFO|glassfish3.1.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=133;_ThreadName=Thread-2;|GRIZZLY0021: " Grizzly running on SunOS - 5.10 under JDK version: 1.6.0_30 - Sun Microsystems Inc. port: 8280 Thread Pool: com.sun.enterprise.v3.services.impl.monitor.MonitorableThreadPool@4b9772e2, port=8280 Read Selector: 3 ByteBuffer size: 4096 maxHttpHeaderSize: 4096 sendBufferSize: 8192 maxKeepAliveRequests: 10,000 keepAliveTimeoutInSeconds: 120 Static File Cache enabled: false Static resources directory: /opt/server/glassfish3/glassfish/domains/comet/docroot Adapter : com.sun.enterprise.v3.services.impl.ContainerMapper Asynchronous Request Processing enabled: true|#]

    Java.net JIRA | 5 years ago | guillaume.d
    java.util.concurrent.RejectedExecutionException: The thread pool's task queue is full, limit: 4096
  3. 0

    Periodical error on Glassfish after a small load and running for a few hours. No one is connected to the server anymore and the error appear a few hours after a stress test. The questions are : * how is it possible that the such an error appear when there is no more load ? * since no requests are made, what is filling the pool ? * can we see which request fill in the pool ? can we activate any logs ? Thanks. The error : {noformat} [#|2012-02-02T19:43:24.375+0100|SEVERE|glassfish3.1.1|grizzly|_ThreadID=119;_ThreadName=Thread-2;|doSelect exception java.util.concurrent.RejectedExecutionException: The thread pool's task queue is full, limit: 4096 at com.sun.grizzly.util.AbstractThreadPool.onTaskQueueOverflow(AbstractThreadPool.java:473) at com.sun.grizzly.util.QueueLimitedThreadPool.onTaskQueueOverflow(QueueLimitedThreadPool.java:97) at com.sun.grizzly.util.QueueLimitedThreadPool.execute(QueueLimitedThreadPool.java:88) at com.sun.grizzly.util.GrizzlyExecutorService.execute(GrizzlyExecutorService.java:162) at com.sun.grizzly.http.StatsThreadPool.execute(StatsThreadPool.java:127) at com.sun.grizzly.NIOContext.execute(NIOContext.java:510) at com.sun.grizzly.NIOContext.execute(NIOContext.java:488) at com.sun.grizzly.SelectorHandlerRunner.handleSelectedKey(SelectorHandlerRunner.java:370) at com.sun.grizzly.SelectorHandlerRunner.handleSelectedKeys(SelectorHandlerRunner.java:263) at com.sun.grizzly.SelectorHandlerRunner.doSelect(SelectorHandlerRunner.java:200) at com.sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java:132) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) |#] {noformat} Glassfish connector config : [#|2012-02-02T19:43:26.844+0100|INFO|glassfish3.1.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=133;_ThreadName=Thread-2;|GRIZZLY0021: " Grizzly running on SunOS - 5.10 under JDK version: 1.6.0_30 - Sun Microsystems Inc. port: 8280 Thread Pool: com.sun.enterprise.v3.services.impl.monitor.MonitorableThreadPool@4b9772e2, port=8280 Read Selector: 3 ByteBuffer size: 4096 maxHttpHeaderSize: 4096 sendBufferSize: 8192 maxKeepAliveRequests: 10,000 keepAliveTimeoutInSeconds: 120 Static File Cache enabled: false Static resources directory: /opt/server/glassfish3/glassfish/domains/comet/docroot Adapter : com.sun.enterprise.v3.services.impl.ContainerMapper Asynchronous Request Processing enabled: true|#]

    Java.net JIRA | 5 years ago | guillaume.d
    java.util.concurrent.RejectedExecutionException: The thread pool's task queue is full, limit: 4096
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Hazlecast timeout issue

    Google Groups | 3 years ago | Bing
    java.util.concurrent.RejectedExecutionException: The thread pool's task queue is full, limit: 4096

    1 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.util.concurrent.RejectedExecutionException

      The thread pool's task queue is full, limit: 4096

      at org.glassfish.grizzly.threadpool.AbstractThreadPool.onTaskQueueOverflow()
    2. Grizzly
      AbstractThreadPool$Worker.run
      1. org.glassfish.grizzly.threadpool.AbstractThreadPool.onTaskQueueOverflow(AbstractThreadPool.java:490)
      2. org.glassfish.grizzly.threadpool.QueueLimitedThreadPool.execute(QueueLimitedThreadPool.java:81)
      3. org.glassfish.grizzly.threadpool.GrizzlyExecutorService.execute(GrizzlyExecutorService.java:161)
      4. org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.executeIoEvent(WorkerThreadIOStrategy.java:100)
      5. org.glassfish.grizzly.strategies.AbstractIOStrategy.executeIoEvent(AbstractIOStrategy.java:89)
      6. org.glassfish.grizzly.nio.SelectorRunner.iterateKeyEvents(SelectorRunner.java:415)
      7. org.glassfish.grizzly.nio.SelectorRunner.iterateKeys(SelectorRunner.java:384)
      8. org.glassfish.grizzly.nio.SelectorRunner.doSelect(SelectorRunner.java:348)
      9. org.glassfish.grizzly.nio.SelectorRunner.run(SelectorRunner.java:279)
      10. org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:591)
      11. org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:571)
      11 frames
    3. Java RT
      Thread.run
      1. java.lang.Thread.run(Unknown Source)
      1 frame