Does anyone have any tips on how to configure Camel to be more performant on WebSphere MQ? I haven't seen any settings to allow MQ to use connection pooling and I'm finding that it isn't performing well under load - I suspect due to the overhead of opening and closing connections (it's about twice as slow as the same service over HTTP). I have set the JMS consumer to have 30 concurrent consumers and this helped a little.
I have tried adding the following line to the Spring configuration to no avail: <bean class="org.springframework.beans.factory.config.MethodInvokingFactoryBean" p:staticMethod="com.ibm.mq.MQEnvironment.addConnectionPoolToken" /> Is there anything else that I can do? Is anyone using MQ with Camel in a high performance environment? Thanks, Damian. -- View this message in context: http://camel.465427.n5.nabble.com/How-to-improve-Camel-MQ-performance-tp3334208p3334208.html Sent from the Camel - Users mailing list archive at Nabble.com.
