activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Cons (Created) (JIRA)" <>
Subject [jira] [Created] (APLO-185) Apollo can send STOMP messages without a destination header (advisories)
Date Thu, 05 Apr 2012 06:44:09 GMT
Apollo can send STOMP messages without a destination header (advisories)

                 Key: APLO-185
             Project: ActiveMQ Apollo
          Issue Type: Bug
         Environment: apollo-99-trunk-20120404.190241-13
            Reporter: Lionel Cons

As discovered by accident in the console, recent Apollo snapshots use the following topics:
ActiveMQ.Advisory.Topic and ActiveMQ.Advisory.Queue.

When trying to consume messages from these, the messages do not contain a "destination" header,
this way violating the STOMP 1.1 spec.

Here is an example (the body contains binary characters):

  'body' => t{)ID:xxx-21826-1333604711518-0:0eActiveMQ.Advisory.Queuen{)ID:xxx-21826-1333604711518-0:0AdvisoryoriginBrokerId
  'header' => {
    'content-length' => '378',
    'content-type' => 'protocol/openwire',
    'message-id' => 'apollo-5418',
    'subscription' => '8988460-4f7d3c07-589d-fa9a-6'

Could the "destination" header be added please?

This also brings other questions:

(1) why does Apollo generate protocol/openwire messages although I did not enable OpenWire?

(2) if these advisories are useful without OpenWire, the body should be easier to parse (e.g.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message