-
Bug
-
Resolution: Done
-
Major
-
7.3.x
Provide a way to configure maximumPoolSize of ServerService Thread Pool. It defaults to Integer.MAX_VALUE and it's unable to be changed in the current implementation:
446 public synchronized void start(StartContext context) throws StartException { 447 executorService = new ThreadPoolExecutor(0, Integer.MAX_VALUE, 20L, TimeUnit.SECONDS, 448 new SynchronousQueue<Runnable>(), threadFactory); 449 }
Though the threads will disappear after 20 seconds of finishing a task, ulimit (nproc, max user processes) has a possibility to run out and "java.lang.OutOfMemoryError: unable to create new native thread" would occur depending on deployed applications. For example, an application coming with many <persistence-unit> entries in persistence.xml or a lot of @Startup @Singleton EJB can cause spawning a lot of ServerService Thread Pool thread.
Even if ulimit can be configurable and it is recommended to be tuned in a production environment, making maximumPoolSize of ServerService Thread Pool configurable would be helpful.
- clones
-
WFCORE-1934 Make number of thread size for ServerService Thread Pool configurable
- Closed
- is cloned by
-
JBEAP-22150 [GSS](7.3.z) WFCORE-1934 - Make number of thread size for ServerService Thread Pool configurable
- Closed
- is incorporated by
-
JBEAP-21978 (7.4.z) Upgrade WildFly Core from 15.0.2.Final-redhat-00001 to 15.0.3.Final-redhat-00001
- Closed
- links to