Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 9 Apr 2012 20:39:19 +0000 (UTC)
From: "Hiram Chirino (Commented) (JIRA)" <jira@apache.org>
To: commits@activemq.apache.org
Message-ID: 
 <2091426152.4584.1334003959726.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1687835457.16045.1333608249424.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (APLO-185) Apollo can send STOMP messages
 without a destination header (advisories)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/APLO-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250158#comment-13250158 ] 

Hiram Chirino commented on APLO-185:
------------------------------------

I've also now changed this so that the Advisory topic is not created until the topic is subscribed to.  Helps keep the Openwire support hidden until it's fully supported and documented.
                
> Apollo can send STOMP messages without a destination header (advisories)
> ------------------------------------------------------------------------
>
>                 Key: APLO-185
>                 URL: https://issues.apache.org/jira/browse/APLO-185
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>         Environment: apollo-99-trunk-20120404.190241-13
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.2
>
>
> 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)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira