In order to increase performance in our production environment (AEM 6.2, servicepack 1), we want to increase min poolsize and max poolsize for org.apache.sling.commons.threads.impl.DefaultThreadPool.
Pool default handles an enormous amount of tasks, with pool size 5.
Pool default
- used : true
- min pool size : 5
- max pool size : 5
- queue size : -1
- keep alive time : 60000
- block policy : RUN
- priority : NORM
- shutdown graceful : true
- shutdown wait time : -1
- daemon : false
- active count : 1
- completed task count : 9600555
- core pool size : 5
- largest pool size : 5
- maximum pool size : 5
- pool size : 5
- task count : 9600556
There are several threads discussing this issue (like How to increase no of threads to run concurrently in AEM 6.1 ). But these threads solves the issue creating new factory configurations (a separate named thread pool). We will need to rewrite the entire application, to be able to send all requests to new named thread pools.
Trying to change DefaultThreadPool inside Adobe Experience Manager Web Console Configuration is not possible:
![threadpool.PNG threadpool.PNG](/t5/image/serverpage/image-id/6171i25A83CBC807E5F36/image-size/large?v=v2&px=999)
Are there any ways to increase DefaultThreadPool default-values, without having to manipulate metatype.xml inside org.apache.sling.commons.threads.jar GC: OSGI-INF / metatype / metatype.xml - GrepCode Source ?
Best regards
Henrik Heiestad