[jboss-jira] [JBoss JIRA] (WFLY-7647) Configure Artemis thread pool size without reload

[Jeff Mesnil (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469779#comment-13469779 ] 

Jeff Mesnil commented on WFLY-7647:
-----------------------------------

The thread-pool-max-size is handled by Artemis in its configuration.

Changing this value on the fly will have no consequence until Artemis is restarted.
In order to do that, you will have to open an upstream issue in ARTEMIS to ask them to be able to change thread pool size at runtime.

> Configure Artemis thread pool size without reload
> -------------------------------------------------
>
>                 Key: WFLY-7647
>                 URL: https://issues.jboss.org/browse/WFLY-7647
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: JMS
>    Affects Versions: 10.1.0.Final
>            Reporter: Martin Styk
>            Assignee: Jeff Mesnil
>
> Currently, thread pool size can not be adjusted without server reload. If server runs into performance problem caused by thread pool size, there is no way to adjust thread pool size without termination of all running tasks. Making this configurable "on fly" would prevent this scenario. 
> Attribute {{thread-pool-max-size}} in {{/subsystem=messaging-activemq/server=default}} requires server reload.
> Size of global client thread pools can be set only before this thread pool is created. Adjusting values of system properties which configure client thread pool size has no effect on running server (with pool already created). 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)