Ad 2) You can read about receiveTimeout in spring jms documentation as well, as camel-jms is built on top of spring jms. So the option is from spring.
Its default 1000 (eg 1 sec). On Tue, Oct 15, 2013 at 9:41 PM, saran_kct <saran_...@yahoo.co.in> wrote: > Thank You Claus. I tried setting that option, no luck. I have 2 questions > > 1) JMS Connection Pool - Is there any reference documentation that you can > point me to set this up in Camel - Spring - IBM MQ > > 2) I tried setting > ibmmq://queue:CCGD.DDCTM.IN2?*cacheLevelName=CACHE_CONSUMER*&maxConcurrentConsumers=2&transacted=true, > no luck. But we noticed it was less chatty when we set > > ibmmq://queue:CCGD.DDCTM.IN2?*receiveTimeout=300000*&maxConcurrentConsumers=2&transacted=true > > I am not sure of the impact of receiveTimeout attribute. > http://camel.apache.org/jms says "The timeout for receiving messages (in > milliseconds).", I am not understanding what this means. I also noticed > that, when I undeployed my application after adding receiveTimeout=300000 - > it took a while ( > 2 mins )for the camel context to shutdown. Before this > attribute - it was immediate. > > Thanks for your time! > > Thanks > Saran > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-JMS-Container-sending-1000-s-of-ping-like-messages-in-a-minute-to-IBM-MQ-tp5741547p5741617.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen