Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 11 May 2012 15:00:51 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <221754239.54686.1336748451027.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1620373113.54599.1336746770443.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3836) STOMP 1.0 protocol (SUBSCRIBE
 destination) broken on ActiveMQ 5.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timothy Bish commented on AMQ-3836:
-----------------------------------

StompTest.java in our unit tests has plenty of examples, barring that please create a test case using the client you are currently using.  
                
> STOMP 1.0 protocol (SUBSCRIBE destination) broken on ActiveMQ 5.6.0
> -------------------------------------------------------------------
>
>                 Key: AMQ-3836
>                 URL: https://issues.apache.org/jira/browse/AMQ-3836
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: stomp
>    Affects Versions: 5.6.0
>         Environment: Centos 5 running Apache ActiveMQ 5.6.0, jre-1.6.0_20-fcs
>            Reporter: Deives Michellis
>
> Destination specification on STOMP using activemq 5.6.0 is broken.
> Before 5.6.0, you had to specify "/queue/my_queue". Now, activemq automatically includes a "/queue/" on destination name, whether needed or not.
> For instance, sending messages to "/queue/nagios-events" works. Subscribing to "/queue/nagios-events" creates an additional queue named "/queue/queue/nagios-events".
> Message sending is also affected, although it accepts both "/queue/nagios-events" and "nagios-events"

--
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