camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Resource lock, endpoint calling it self in for-loop
Date Wed, 17 Sep 2014 06:58:23 GMT
Yes you are blocking the thread with the requestBody method call, and
sending to yourself. So you end up with no available consumer to
pickup and process the messages. If you use another queue then you
dont send to yourself, and therefore have available consumers to
process and send back the reply message, so the request body method
can get the result and continue.

And btw sending messages to yourself is likely not a good design.


On Wed, Sep 17, 2014 at 8:27 AM, frodejoh <frode@johansens.net> wrote:
> Forgot to specify:
> Tried on Camel v. 2.13.0 and 2.13.2
>
> Would be nice if someone could help out. The given example should be enough
> to create a little use case to demonstrate the problem.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Resource-lock-endpoint-calling-it-self-in-for-loop-tp5756095p5756627.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Mime
View raw message