camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From contactreji <>
Subject RE: JMS MQ performance improvement
Date Mon, 08 Jun 2015 10:11:06 GMT

Can you try using pooled jms connections?
It may be possible that due to initialization of new connection each time
for each message, internally thread size may be limited to have optimized
thread context switching.

Following few code snipped might help you. We have used this in our project
and observed increase in throughput. Not sure if IBM product supports
connection pools. Check the IBM driver classes.

We were using Jboss ActiveMQ as broker.

	<bean id="jmsConnectionFactory"
		<property name="brokerURL" value="${brokerURL}" />
		<property name="userName" value="${brokerUserName}" />
		<property name="password" value="${brokerPassword}" />
	<bean id="pooledConnectionFactory"
		init-method="start" destroy-method="stop">
		<property name="maxConnections" value="8" />
		<property name="connectionFactory" ref="jmsConnectionFactory" />
		<property name="idleTimeout" value="0" />
	<bean id="jmsConfig"
		<property name="connectionFactory" ref="pooledConnectionFactory" />
		<property name="concurrentConsumers" value="10" />

	<bean id="AMQbrokerConnector"
		<property name="configuration" ref="jmsConfig" />

Reji Mathews
Sr. Developer - Middleware Integration / SOA ( Open Source - Apache Camel & Jboss Fuse
ESB | Mule ESB )
LinkedIn -
Twitter - reji_mathews
View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message