You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Abdeslam El Abbassi <ab...@thalesgroup.com> on 2007/12/11 17:47:28 UTC
Re: why JMS component create a new correlationID

Hi ,
i use the useMsgIdInResponse attribute to keep the same correlationID when a
jms consumer is used, but not working.

Have you an idea to force the consumer jms:endpoint to use the same
correlationID and to not create it ?

Regards,

Abdes





Abdeslam El Abbassi wrote:
> 
> 
> 
> 
> 
> 
> Hi, 
> i try to solve this problem : keeping the same correlation ID in all my
> pattern (Flow). 
> My flow is HTTP &gt; SU (send message with JMS) &gt; EIP Pipeline (
> XSLT and JMS) 
> 
> All is correct, but when la last JMS consume the message , it create a
> new correlationID. 
> 
> I try to resolve this by using useMsgIdInResponse="true" but not
> working. 
> 
> &nbsp;&nbsp;&nbsp;&nbsp; &lt;jms:endpoint service="f087:jms3" 
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
> endpoint="jms4" 
> &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
> &nbsp;&nbsp;&nbsp; &nbsp; targetService="f087:wiretapsetflow2" 
> &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
> &nbsp;&nbsp;&nbsp; &nbsp; targetEndpoint="wiretapsetflow2" 
> &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; role="consumer" 
> &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
> &nbsp;&nbsp;&nbsp; &nbsp; destinationStyle="queue" 
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
> jmsProviderDestinationName="${queue.cible}" 
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
> connectionFactory="#connectionFactory" 
> &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
> &nbsp;&nbsp;&nbsp; &nbsp; defaultMep=
> "http://www.w3.org/2004/08/wsdl/in-out" 
> &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
> &nbsp;&nbsp;&nbsp; &nbsp; useMsgIdInResponse="true" 
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
> &nbsp;&nbsp;&nbsp; &nbsp; /&gt; 
> 
> 
> 
> log : 
> 13:52:22,933 | DEBUG | pool-component.servicemix-jms-thread-3 |
> JmsComponent&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
> | emix.common.AsyncBaseLifeCycle&nbsp; 587 |
> Created correlation id: ID:142.1.153.67-1163e5dbd9c-7:1 
> 
> 
> Regards, 
> 
> Abdeslam El Abbassi 
> Thales Services 
> 
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/why-JMS-component-create-a-new-correlationID-tp13747563s12049p14277867.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.