camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem jiang <>
Subject Re: Issue during concurrent inOut Queue Call
Date Thu, 25 Oct 2012 09:32:17 GMT

It could be helpful if you can show us your camel route definition.

Willem Jiang

Red Hat, Inc.
FuseSource is now part of Red Hat
Web: |
Blog: ( (English)
 ( (Chinese)
Twitter: willemjiang 
Weibo: willemjiang

On Thursday, October 25, 2012 at 5:04 PM, uemit2705 wrote:

> Hi there,
> i have an issue in my tomcat application while calling an inout queue
> concurrently. 
> There are 5 consumers listening concurrently to a queue in an "outer" route,
> and in this route we placed a further concurrent (8 Consumer) inout
> FileUpload queue where further processing takes place. There are no
> FileUpload issues, all 9 Tables are Uploaded correctly with SqlLoader to
> Oracle, but no answer reaches the "outer" calling route. After i have
> analyzed both contexts over JMX, i found out that the concurrent inout
> FileUpload Queue completes all 9 Exchanges, but only 5 exchanges arrive at
> the "calling context". 
> Naming issues (e.g. clashes / collisions) or any lowlevel issues can be
> excluded.
> Now my concrete Question: Might this be an issue with the ActiveMQ temporary
> Queue, or are we following some "Non-Camel-like" design pattern of or
> contexts? Is there anybody who has experienced an issue like this and who
> can give us some tips for a workaround? I would be also glad, if you could
> point to some trace spots.
> Thanks in advance for your help!
> Kind regards, 
> uemit2705
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at (

View raw message