To increase performance, use caching of connection. We used the same and are able to process a huge volume.
<!-- Queue Manager Connection factory(s) --> <bean id="wmqConnectionFactory1-Prod1-FIT" class="com.ibm.mq.jms.MQQueueConnectionFactory"> <property name="CCDTURL"> <bean class="com.tgt.tcom.il.financial.MQConnectionFactoryUtil" factory-method="convert"> <argument value="${financial.WMQ.CCDTfile}" /> </bean> </property> <property name="queueManager" value="${financial.WMQ.QMGrpName1}" /> </bean> <!-- Cache Connection Factory --> <bean id="cachingWmqConnectionFactory1-Prod1-FIT" class="org.springframework.jms.connection.CachingConnectionFactory" destroy-method="destroy"> <property name="targetConnectionFactory" ref="wmqConnectionFactory1-Prod1-FIT" /> <property name="cacheConsumers" value="true" /> <property name="reconnectOnException" value="true" /> <property name="sessionCacheSize" value="10" /> </bean> <!--Spring Transaction Manager --> <bean id="wmqTransactionManager1-Prod1-FIT" class="org.springframework.jms.connection.JmsTransactionManager"> <property name="connectionFactory" ref="wmqConnectionFactory1-Prod1-FIT" /> </bean> <!--JMS components used for Endpoints --> <bean id="wmq-qm1-Prod1-FIT" class="org.apache.camel.component.jms.JmsComponent"> <property name="connectionFactory" ref="cachingWmqConnectionFactory1-Prod1-FIT" /> <property name="transactionManager" ref="wmqTransactionManager1-Prod1-FIT" /> <property name="transacted" value="false" /> <property name="cacheLevelName" value="CACHE_AUTO" /> <property name="concurrentConsumers" value="${financial.WMQ.DWSub1.Consumers}" /> <property name="maxConcurrentConsumers" value="${financial.WMQ.DWSub1.MaxConsumers}" /> <property name="maxMessagesPerTask" value="${financial.WMQ.DWSub1.maxMessagesPerTask}" /> </bean> Thanks and Regards, Vanshul Chawla -----Original Message----- From: mytechnology [mailto:mytech1...@gmail.com] Sent: Tuesday, July 28, 2015 6:05 PM To: users@camel.apache.org Subject: RE: JMS MQ performance improvement Why is it so hard (so far impossible) to find a way of configuring connection pool with IBM MQ. All the documentation is with websphere MDBs or ActiveMQ and Camel. Has any body used connection pool with IBM MQ and Camel? -- View this message in context: http://camel.465427.n5.nabble.com/JMS-MQ-performance-improvement-tp5767963p5770010.html Sent from the Camel - Users mailing list archive at Nabble.com.