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: Question about how default camel exchange pattern is being set
Date Fri, 04 Jul 2014 07:31:50 GMT
Its the consumer which creates the Exchange that sets the initial MEP.

On Thu, Jul 3, 2014 at 4:20 PM, Anthony Scatchell
<AnthonyS3@discovery.co.za> wrote:
> Hey everyone,
>
> I’ve been googling around for this without much luck, trying to figure out how the
default camel exchange pattern is set, and what might affect it in our routes (besides the
setExchangePattern node.)
>
> Problem is, in an onException block we’re trying to place a message on a queue, and
this message is timing out waiting for a response from the queue. We found out this is because
somehow the exchange pattern is being set to inOut which mandates a request-reply pattern,
expecting a reply from the queue, which it never gets.
>
> Have solved the problem in the short term by making to <to/> node to the jms queue
<inOnly/> instead. It works fine but the weird part is, we never saw failures like this
in our tests. After some investigation, it seems in all our tests the default exchange pattern
for everything in the routes is InOnly, and whenever we deploy, the default for all the routes
seems to be InOut. Not sure what is causing this difference.
>
> So, just wondering what can alter the default exchange pattern when using camel, as we
aren’t setting it explicitly.
>
> We’re using xml to write our routes, and are on version 2.11.0 of camel.
>
> Any help is much appreciated, thanks!
>
> —Anthony
> Discovery is an authorised financial services provider.
>
> The information in this email is confidential and may have legal privileges. We intend
it only for the use of the individual or entity we've addressed the communication to. If you
have received this email by mistake please delete it and tell the sender. We forbid any unauthorised
use, change, disclosure or sending of the contents of this email (including its attachments),
whether in part or as a whole, unless consented to in writing by the sender, as it may be
unlawful.
>
> We cannot guarantee this email has no malicious coding.
>
> We reserve the right to check, intercept and block emails or take any other action according
to our email etiquette.
>
> Discovery will not be liable for any delivery delay, loss, harm, disruption or data corruption
that may arise from this email.
>
> A full list of company directors is available on our website at: https://www.discovery.co.za/info/directors
- or to get this list by email, please email directors_list@discovery.co.za



-- 
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