Resource Adapter Configurations - Relation between mdb max-pool-size and maxsession and resource-adapter min/max-pool-size

Solution Verified - Updated -

Issue

  • We have mdb max-pool-size and in application we can set maxSession too.
<bean-instance-pools>
<strict-max-pool name="slsb-strict-max-pool" max-pool-size="40" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="mdb-strict-max-pool" max-pool-size="40" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
  • And we have resource-adapter min/max-pool-size:
<connection-definition class-name="org.apache.activemq.ra.ActiveMQManagedConnectionFactory" jndi-name="java:/ConnectionFactory" enabled="true" use-java-context="true" pool-name="ConnectionFactory">
<xa-pool>
<min-pool-size>10</min-pool-size>
<max-pool-size>100</max-pool-size>
</xa-pool>
  • I understand that maxSession should not be greater than mdb max-pool-size.
  • But how is pool-size ActiveMQManagedConnectionFactory related to mdb max-pool-size. How should we set it in relation to mdb's max-pool-size and maxSession

Customer query specifically is:

“EAP level we have the mdb pool size to 65 , and we have set the max session to be 65 on the application level. our mdb application is consuming from AMQ and it’s replying to a different reply queue. so in this case please advise what’s the min and max pool size that should be assigned for the connection factory of the resource adapter of AMQ. should it be for example 65+1 ? “
  • Any suggestions here ?

Environment

  • Red Hat AMQ
    • 6.3.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In