[
https://issues.apache.org/jira/browse/AMQ-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Hudson updated AMQ-3836:
-----------------------------
Attachment: firsttony.php
modified first.php from fuse stomp php client. the result on 5.5.1 comes back
as:
Notice the destination has a /queue on it in 5.6.0 We checked the STOMP frame
and its not coming from the client.
In 5.5.1 we get this result:
Received headers
s_scale => 0.001
message-id => ID:tony-desktop-53600-1338396365864-2:12:-1:1:1
d_serviceName => ModelUpload
destination => /topic/testtopic
timestamp => 1338399414341
s_modelID => 123456
expires => 0
priority => 4
In 5.6.0 we get this result:
Received headers
s_scale => 0.001
message-id => ID:maker-55961-1338400788753-2:2:-1:1:1
d_serviceName => ModelUpload
destination => /queue//topic/testtopic
timestamp => 1338401617112
s_modelID => 123456
expires => 0
priority => 4
Here is the frame that was sent:
SEND
d_serviceName: ModelUpload
s_modelID: 123456
s_scale: 0.001
destination: /topic/testtopic
test
---
I suspect its something in the FrameTranslator, digging in there.
> 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
