camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: activemq with InOut pattern - problem
Date Mon, 26 Jul 2010 15:00:35 GMT

What kind of object type do you send over JMS? if you send serialized
objects then make sure the client can de-serialize the data.
If its XML based then maybe use TextMessage instead.

You can configure the JMS endpoint to force it to send text messages

By setting this in the endpoint uri

Otherwise do some logging/tracing, enable DEBUG/TRACE logging to see
what AMQ returns back.

2010/7/26 Paweł Wesołowski <>:
> Hi,
> Recently I've tried to use activemq component with pattern="InOut".
> <route id="r1">
>    ...
> <to uri="activemq:queue:undelivered.msgs?requestTimeout=600000"
> pattern="InOut" />
>    ...
> </route>
> <route id="r2">
> <from uri="activemq:queue:undelivered.msgs" />
>    ...
> </route>
> Everything is ok except the fact that the body part of the message is empty
> when it comes back from queue. Before message is returned by r2 to r1 body
> contains SOAPMessage object, but the response seen by r1 has empty body.
> Am I doing something wrong? I have tired to use other options in avtivemq
> uri like alwaysCopyMessage=true but it hasn't helped me at all.
> I'm using fuse esb with camel version 2.2.0.
> --
> Paweł Wesołowski

Claus Ibsen
Apache Camel Committer

Author of Camel in Action:
Open Source Integration:

View raw message