[ https://issues.jboss.org/browse/WFLY-6513?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-6513: ------------------------------------ Things to consider before implementing this: * the thread pool is currently managed by {{org.jboss.as.weld.services.bootstrap.WeldExecutorServices}} and only used during application bootstrap (Weld 2.3) * will be probably used during runtime for async events in the future (Weld 3.0) * {{WeldExecutorServices}} has {{ServiceController.Mode.ON_DEMAND}} initial mode, i.e. it's stopped when no CDI application is running * even though the max thread pool size is taken into account, it might be ignored - the current implementation takes no more than {{Runtime.getRuntime().availableProcessors()}} threads during bootstrap I think it does not make sense to allow the users to configure the thread pool size for now. Though, it might be reasonable to set a hard coded keep alive time for the thread pool, similarly to [TimingOutFixedThreadPoolExecutorServices|https://github.com/weld/core/blo...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)