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

When the Artemis Resource Adapter is configured for connection with external AMQ, the max-pool-size attribute is ignored

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • None
    • JMS
    • None
    • Undefined

    Description

      When the internal artemis resource adapter is configured for connection to an external AMQ 7 instance. seeting max-pool-size on the resource adapter connection factory seems to have no effect. For example, if the max-pool-size is configured with a value of "10"

      <pooled-connection-factory name="activemq-ra-remote" entries="java:/RemoteJmsXA java:jboss/RemoteJmsXA java:jboss/DefaultJMSConnectionFactory" connectors="netty-remote-throughput-node1" transaction="xa" user="admin" password="admin" ha="true" max-pool-size="10"/>

      but an MDB with a maxSession attribute of "100" is deployed:

      @MessageDriven(name = "InboundQueueMDB", activationConfig = {
    @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
    @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "100"),
    @ActivationConfigProperty(propertyName = "destination", propertyValue = "INBOUND_QUEUE") })
@ResourceAdapter(value="activemq-ra-remote")

      we can see 100 (actually 101) individual connections between the JBoss EAP instance and the external AMQ instance, with one session per connection.

      Attachments

        Issue Links

          clones

          Feature Request - Feature requests from customers and/or users JBEAP-21562 [GSS](7.4.z) When the Artemis Resource Adapter is configured for connection with external AMQ, the max-pool-size attribute is ignored

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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-5133 Resource Adapter Support for Shared Connections

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

          Web Link ARTEMIS-3539

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              ehugonne1@redhat.com Emmanuel Hugonnet
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: