CODEWITHSUNDEEP
springactivemq-classicspring-integrationspring-jms
Anuj Khandelwal
Anuj Khandelwal

Reputation: 845

How to create multiple listeners in ActiveMQ using spring JMS

I have a use case where I want to create multiple listeners(6) in an application. I want to subscribe to multiple destinations(6 topics). All the subscription are durable. I am using separate default message listener container(DMLC) for each listener and using different client id but I am confused about how connection factory should be used.

Should I use single ActiveMQ pooled connection factory with maxConnection specified to 6. OR should I use different pooled connection factory for each listener ?
Is there any harm is using pooledConnectionFactory with maxConnection for durable subscriber?

Source code:
Connection Factory: 

<bean id="jmsFactory" class="org.apache.activemq.pool.PooledConnectionFactory"
destroy-method="stop">
<property name="connectionFactory">
<bean class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL">
<value>${jms.broker.url}</value>
</property>
</bean>
</property>
<property name="maxConnections" value="6" />

and my listener is using it as: (I have 6 similar listeners similar to this using different destinations and client ID)

<bean id="listenerContainer"
class="org.springframework.jms.listener.DefaultMessageListenerContainer"

      <property name="connectionFactory" ref="jmsFactory" />
      <property name="destination" ref="topic_pnlCompleteTopic" />
      <property name="durableSubscriptionName" value="FAGCompletion" />
      <property name="pubSubDomain" value="true" />
      <property name="subscriptionDurable" value="${jms.fagsListener.durable}" />
      <property name="clientId" value="${jms.fagsListener.clientId}" />
      <property name="messageListener" ref="pnlMessageListener" />
      <property name="messageSelector" value="JMSType = 'FAG Completion'" />
 </bean>

Upvotes: 2

Views: 3056

Answers (2)

Petter Nordlander
Petter Nordlander

Reputation: 22279

You listeners will typically only use one session each, since you are using topics. There is no reason to specify a limit on your pool, or to use multiple pools. You typically use one pooled connection factory for your application unless you see a real reason to limit or split it up into different pools.

Upvotes: 1

Stephane Nicoll
Stephane Nicoll

Reputation: 33091

That sounds all fine to me as long as you're not using this connection factory for something else. There is no reason to limit the number of connections to 6, you can put a higher number if you want and it will be only used if necessary. ConnectionFactory is typically the thing that you share for your whole app. See it as a kind of DataSource for JMS access

Upvotes: 1

Related Questions