yogu13 wrote
> ok .. i got the code working, i was mistaken to think there was a timeout
> happening, but actually there wasnt..
>
> All is good now..
>
> Thank you!
>
> Regards,
> -Yogesh
Dear Yogesh,
I am facing same behavior, with Camel (2.12.4) JMS Endpoint and Websphere
(8.5.5.5) MQ conne
ok .. i got the code working, i was mistaken to think there was a timeout
happening, but actually there wasnt..
All is good now..
Thank you!
Regards,
-Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jms-asyncStartListener-Issue-tp5767551p5767816.html
Sent from
Spliting the logic and taking less time for creation of connection worked...
There seems to be a timeout happening somewhere underneath Let me see if i
can build a testcase to showcase this.
Regards,
-Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jms-asyncSta
Hello Claus,
I understand what you say ... but what puzzles me is when asyncStartListener
is set to false .. it works like a charm.. if a timeout was happening it
should have been consistent.
I am going to try splitting the logic for creation of InitialContext and
actual creation of connection fr
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.
