[APLO-185] Apollo can send STOMP messages without a destination header (advisories)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2
• Environment: apollo-99-trunk-20120404.190241-13
• Assignee: Hiram R. Chirino
• Reporter: Lionel Cons
• Created: 05/Apr/12 06:43
• Updated: 09/Apr/12 20:38
• Resolved: 09/Apr/12 19:35

Description

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 NOT_SETd?monitor.test.yyy.apollo.xxx.stomp',
'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. JSON)