[
https://issues.apache.org/jira/browse/AMQ-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286811#comment-13286811
]
Timothy Bish commented on AMQ-3836:
-----------------------------------
Agreed the spec was a bit vague in this regard. In 5.6 we removed the header
trimming in order to not discard spaces that a client had intentionally placed
there. It might be good to at least do a test on a trimmed destination value
before assuming its a queue and getting into this scenario.
> 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
> Attachments: firsttony.php
>
>
> 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
