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.
- is cloned by
-
WFLY-16047 When the Artemis Resource Adapter is configured for connection with external AMQ, the max-pool-size attribute is ignored
-
- Pull Request Sent
-
- relates to
-
ENTMQBR-5133 Resource Adapter Support for Shared Connections
-
- Closed
-
- links to
