Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6590

Client thread pool max size parameter should be possible to parametrize in CLI

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Duplicate
    • Major
    • None
    • 10.0.0.Final
    • JMS
    • None

    Description

      Based on discussion in JBEAP-2947, we should provide CLI parameter to set maximum size of client thread pool.

      Currently -Dactivemq.artemis.client.global.thread.pool.max.size=<value> must be provided as system property during start of EAP 7 server.

      This thread pool can be injected by Wildfly. This could be the way to limit make its size configurable by Wildfly

      Attachments

        Issue Links

          duplicates

          Feature Request - Feature requests from customers and/or users WFLY-7648 Allow configuration for ActiveMQ client thread pools

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-6330 Problems with ActiveMQ-client-global-threads

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: