Its using the connection factory to create the connection, so any timeout must come from the vendor of the jms client if they offer such kind.
ActiveMQ has connection timeout options etc. Camel uses the JMS API and there is no such timeout, so you have to look at WebLogic to see what they offer. On Wed, May 27, 2015 at 6:33 PM, yogu13 <[email protected]> wrote: > Hi, > > I am facing a strange issue when i set asyncStartListener to true for a > camel-jms component. I notice that camel doesn't go ahead and create a > connection (Queue) with the JMS Provider (Weblogic). The only thing is i > have wrapped the ConnectionFactory instead of using the JMS Providers > directly. What i notice is if i set the asyncStartListener to false it > connects to the provider correctly. > > One more thing probably that is worth mentioning here is the wrapped > connection factory would be little slower than the vendors provider as it > does a JNDI lookup in createConnection method. > > i checked the camel-jms code and noticed that incase of asyncStartListener > (true) it uses a ExecutorService, does this service have a timeout of any > kinds within which if a connection isn't received it terminates ? > > is yes can this be changed or can it be overcome ? > > Regards, > -Yogesh > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/camel-jms-asyncStartListener-Issue-tp5767551.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 hawtio: http://hawt.io/ fabric8: http://fabric8.io/
