On top of my head I dont think simple offers re-connection logic.
On Wed, Nov 13, 2013 at 10:03 PM, saran_kct <[email protected]> wrote: > Our Environment is > > JDK - 1.5 > Camel v2.6.0 > Spring v2.5.6 > Jboss v4 > IBM MQ v7 > > Below is our JMS Confiuaration. We have 2 InOnly routes with transacted=true > property. > > <bean id="providerJMSConfig" > class="org.apache.camel.component.jms.JmsConfiguration"> > <property name="requestTimeout" value="80000" /> > <property name="useMessageIDAsCorrelationID" value="true" /> > <property name="disableReplyTo" value="true" /> > <property name="consumerType" value="Simple" /> > </bean> > > Now if we have default consumerType, in the event of Queue Manager restarts > , connection is established automatically by the Camel/Sprring JMS client. > > We have to change the consumerType to Simple as default was sending too many > MQGET()'s and no-op commits as Transaction is handled by IBM MQ. > Simplemessagelistener is not sending those many MQGET()'s and we dont need a > XA transaction in our listener, so we prefer SimpleMessageListener. > > Issue is, in the event of Queue Manager restart - client is not > re-establishing the connection. Is there a way to re-establish the > connection automatically for SimpleMessageListener's ? > > Thanks in advance > > Saran > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/consumerType-Simple-failed-to-reconnect-after-Queue-Manager-restart-tp5743215.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
