Hi, The ticket is resolved and the fix was included in several version lines.
Check out the JIRA ticket itself: https://issues.apache.org/jira/browse/CAMEL-6123. Regards, *Raúl Kripalani* Apache Camel PMC Member & Committer | Enterprise Architect, Open Source Integration specialist http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Tue, Aug 13, 2013 at 12:00 AM, ravi.4indra <ravi.4in...@gmail.com> wrote: > > Hi , > > It would be hlepful if anyone can provide update on the issue. > > > issue as described in jira > > *When performing an InOut JMS exchange with a certain requestTimeout, if > the > reply message > is received in time, but the following formula stands true: > > {{T0 + T1 >= T!}}, where: > > T0 = JMS response time > T1 = remaining route processing time following the reply > T! = requestTimeout > > Then camel-jms will throw an {{ExchangeTimedOutException}} regardless of > the > fact that the > reply was truly received in time.* > > > *Below is the Jira link* > > > http://mail-archives.apache.org/mod_mbox/camel-issues/201303.mbox/%3CJIRA.12635116.1362400893039.31620.1363911195905@arcas%3E > <http:// > http://mail-archives.apache.org/mod_mbox/camel-issues/201303.mbox/%3CJIRA.12635116.1362400893039.31620.1363911195905@arcas%3E > > > > > > > > Thanks > ravi > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Issue-with-requestTimeout-for-camel-jms-component-tp5737179.html > Sent from the Camel Development mailing list archive at Nabble.com. >
