Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-11332

Artemis client uses unbounded thread pool

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.ER1
    • 7.1.0.DR19
    • JMS
    • None

    Description

      Artemis client thread pool can be configured using the messaging-activemq subsystem's global-client-thread-pool-max-size attribute (introduced in 11.0.0.Alpha1).

      By mistake, the default value of this attribute was set to -1 (through the ActiveMQClient.DEFAULT_THREAD_POOL_MAX_SIZE constants).
      This means that unless configured otherwise, the Artemis clients running in the app server (e.g. MDB code) will use an unbounded thread pool.
      The correct configuration is to not have a default value. If that's the case, Artemis will determine the size of the pool depending on the number of processors (8 * Runtime.getRuntime().availableProcessors())

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-8881 Artemis client uses unbounded thread pool

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is documented by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11481 [7.1] Documentation - Configuring Messaging - Default client thread pool size

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11497 [7.1] Migration - Default client thread pool size

          • 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 related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-3750 Define default value for ActiveMQ client thread pool

          • 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.
          • Verified

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              jmesnil1@redhat.com Jeff Mesnil
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: