Hi Abid, On Thu, Dec 2, 2010 at 5:01 AM, Abid Khan-EXT <[email protected]> wrote: > Thanks Hiranya, > > I will try that out and see if it works.
The JMS_COORELATION_ID property should be used when Synapse is acting as the consumer (to set a custom correlation ID on the outgoing response). It doesn't make much sense to use this property when Synapse is acting as the producer. In the producer mode, Synapse expects the consumer to send the request message ID as the correlation ID in the response. Thanks, Hiranya > > Thanks, > Abid > > -----Original Message----- > From: Hiranya Jayathilaka [mailto:[email protected]] > Sent: Wednesday, December 01, 2010 4:28 PM > To: [email protected] > Subject: Re: Help needed: How to use co-rellation-id for JMS messages > > On Thu, Dec 2, 2010 at 4:49 AM, Hiranya Jayathilaka > <[email protected]> wrote: >> On Thu, Dec 2, 2010 at 4:23 AM, Abid Khan-EXT <[email protected]> wrote: >>> Could you also please tell me where would be the corelationId would it be >>> in the SyanpseContext? Or somewhere else? >> >> It should be in the Axis2 MessageContext > > Actually by default Synapse doesn't send a correlation ID on the > outgoing requests. So the replier will set the message ID of the > request as the correlation ID. You can set a correlation ID on the > request if you want by setting the JMS_COORELATION_ID property in > Axis2 scope. > > Thanks, > Hiranya > >> >> Thanks, >> Hiranya >> >>> >>> -----Original Message----- >>> From: Hiranya Jayathilaka [mailto:[email protected]] >>> Sent: Wednesday, December 01, 2010 3:38 PM >>> To: [email protected] >>> Subject: Re: Help needed: How to use co-rellation-id for JMS messages >>> >>> Hi, >>> >>> On Thu, Dec 2, 2010 at 3:33 AM, Abid Khan-EXT <[email protected]> >>> wrote: >>>> Hello all, >>>> >>>> I was trying to find some example on how to set up an endpoint that uses >>>> JMS correlation id mechanism to send reply back to predefined Queue. >>>> >>>> I could not find any would you please guide me. >>> >>> Just add the transport.jms.ReplyDestination parameter to the JMS endpoint. >>> >>> eg: >>> >>> <endpoint> >>> <address >>> >>> uri="jms:/SimpleStockQuoteService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&transport.jms.DestinationType=queue&transport.jms.ReplyDestination=TestReplyQueue"/> >>> </endpoint> >>> >>> Synapse will set the REPLY_TO JMS header on the outgoing request so >>> that the server can look it up and send the response to the >>> TestReplyQueue. >>> >>> Thanks, >>> Hiranya >>> >>>> >>>> Thanks, >>>> Abid >>>> >>> >>> >>> >>> -- >>> Hiranya Jayathilaka >>> Senior Software Engineer; >>> WSO2 Inc.; http://wso2.org >>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>> Blog: http://techfeast-hiranya.blogspot.com >>> >> >> >> >> -- >> Hiranya Jayathilaka >> Senior Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: [email protected]; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> > > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
