[jboss-jira] [JBoss JIRA] (WFLY-10168) Unable to set global-client-thread-pool-max-size without setting global-client-scheduled-thread-pool-max-size and vice versa

[Martin Styk (JIRA)]

Martin Styk created WFLY-10168:
----------------------------------

             Summary: Unable to set global-client-thread-pool-max-size without setting global-client-scheduled-thread-pool-max-size and vice versa
                 Key: WFLY-10168
                 URL: https://issues.jboss.org/browse/WFLY-10168
             Project: WildFly
          Issue Type: Bug
          Components: JMS
            Reporter: Martin Styk
            Assignee: Jeff Mesnil


Logic in messaging integration doesn't allow configuring property {{global-client-thread-pool-max-size}} without setting {{global-client-scheduled-thread-pool-max-size}} and vice versa [1]. It seems that Artemis doesn't have API allowing configuration of single property.

User may want to set only one of these properties.

https://github.com/wildfly/wildfly/blob/6c0a002da2558fd4e4f72ceb034a0633c7b1dafd/messaging-activemq/src/main/java/org/wildfly/extension/messaging/activemq/MessagingSubsystemAdd.java#L114



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)