2 Replies Latest reply on Feb 16, 2010 9:39 AM by Michael Justin

    Stomp destination names using /queue/ prefix

    Michael Justin Novice

      Hello,

       

      in my tests I noticed that the MESSAGE frame contains a destination name syntax which is different from the syntax in the SEND frame:


      send:
      SEND
      destination:jms.queue.ExampleQueue

       

       

       

      received:
      MESSAGE
      timestamp:1266327506116
      redelivered:false
      expires:0
      subscription:{DDF9A5F8-649E-4380-8483-6FA6C8B13A74}
      priority:0
      message-id:19327353399
      destination:/queue/ExampleQueue

       

       

      if the Stomp client message includes a reply-to header, the message will be delivered with a reply-to header and a JMSReplyTo header, which use different syntax. The client tries to read the reply-to header and stumbles because the /queue/ prefix is unexpected. Only in the JMSReplyTo header, the jms.queue prefix is present. Is this by design? In the Stomp+JMS documentation, the Stomp header is 'reply-to'.

       

      send:
      SEND
      destination:jms.queue.ExampleQueue
      reply-to:jms.queue.ExampleQueue

       

       

       

      received:
      MESSAGE
      timestamp:1266326994163
      redelivered:false
      expires:0
      subscription:{55061EA2-2717-4B77-A881-4ECFD71DD5E9}
      priority:0
      message-id:17179869752
      reply-to:/queue/ExampleQueue
      JMSReplyTo:jms.queue.ExampleQueue

      destination:/queue/ExampleQueue