-
Feb 25th, 2008, 11:05 AM
#1
DefaultMessageListenerContainer creates hundreds of jms managed connection
Hello,
i am using a DefaultMessageListenerContainer102 for asynchronous message processing in websphere application server 5.1 and websphere MQ 5.3. It is working stable. But while monitoring websphere by Tivoli Performance Viewer i can see approximately 200 jms managed connections. Only 3 of them are open (the configured number of concurrentConsumers). I can only assume that the DefaultMessageListenerContainer doesn't share the connections. How can i configure the DefaultMessageListenerContainer102 to use the websphere connection pool?
Thanks,
Andre
<bean id="jmsConnectionFactory"
class="org.springframework.jndi.JndiObjectFactoryB ean">
<property name="resourceRef" value="false" />
<property name="jndiName" value="jms/CISTrackQCF" />
</bean>
<!-- this is the Message Driven POJO (MDP) -->
<bean id="messageListener"
class="de.schenker.cis.jms.listener.TrackRequestLi stener">
<property name="messageSender">
<ref bean="messageSender"/>
</property>
<property name="xmlToPojoAndReverseConverter">
<ref bean="xmlToPojoAndReverseConverter"/>
</property>
</bean>
<!-- and this is the message listener container -->
<bean id="listenerContainer"
class="org.springframework.jms.listener.DefaultMes sageListenerContainer102">
<property name="concurrentConsumers" value="3" />
<property name="connectionFactory" ref="jmsConnectionFactory" />
<property name="destination" ref="requestDestination" />
<property name="messageListener" ref="messageListener" />
</bean>
Last edited by Daktari; Feb 25th, 2008 at 11:12 AM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules