Show your camel route. Is there another request/reply in the camel route?

On Wed, Dec 4, 2013 at 12:54 PM, javaG <zenma...@gmail.com> wrote:
>
> I changed the order and now I am subscribe to the reply queue before sending
> message but unfortunately this did not make a difference. ActiveMQ again
> translate reply-to to something else that looks like:
>
> DEBUG | Using JMSReplyTo destination:
> temp-queue://ID:hostname-54680-1386185007293-3:3:1 |
> org.apache.camel.component.jms.JmsProducer | Camel (camel) thread #2 -
> JmsConsumer[myqueue]
>
>
> but reply-to has value /queue/4d6c8410-5d24-11e3-8819-8fa83c5684ca
>
>
> This part of the nodejs code that subsribes and sends the message:
>
>         var tempReplyConsumer = '/queue/'+ uuid.v1();  //
>         var jmsCorrelationID = uuid.v1();
>         console.log('replComsumer: ' +  tempReplyConsumer  + '   
> jmsCorrelationID:
> ' +jmsCorrelationID)
>         var getStateSubscription = client.subscribe(tempReplyConsumer,
> checkStateCallback);
>         client.send("/queue/myqueue", {
>                 priority : 9,
>                  persistent: false,
>                 'reply-to': tempReplyConsumer,
>                 'correlation-id': jmsCorrelationID,
>                 serviceName: 'getState',
>
>
>         });
>
>
>         var checkStateCallback = function(message, headers) {
>                 // called when the client receives a STOMP message from the 
> server
>                 if (message.body) {
>                         console.log("got message with body " + message.body);
>                         getStateSubscription.unsubscribe();
>
>                         res.send(JSON.parse(message.body));
>
>
>                 }
>                 };
>
>
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/Stomp-reply-to-header-get-altered-to-temporary-queue-by-ActiveMQ-in-STOMP-to-JMS-messaging-tp4675061p4675143.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.



-- 
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta

Reply via email to