activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Hudson (JIRA)" <>
Subject [jira] [Commented] (AMQ-3836) STOMP 1.0 protocol (SUBSCRIBE destination) broken on ActiveMQ 5.6.0
Date Wed, 30 May 2012 23:41:24 GMT


Alan Hudson commented on AMQ-3836:

The issue is with STOMP clients that put spaces after values as in destination: /topic/test

The convert destination method in LegacyFrameTranslator does a startsWith("/topic") to detect

The fuse stomp php client puts a space on items.  My read of the stomp spec shows examples
without it.  But it doesn't really make it clear.  We're looking around at a few other clients
to see what they do.

If its common of clients then it might make sense to deal with it on the server.  The other
php stomp client does not put spaces in its values.  

I can easily make a junit test for this case if you want it, but I kinda expect this will
be labeled under "client error" or maybe incomplete spec language(my pet peeve).  
> STOMP 1.0 protocol (SUBSCRIBE destination) broken on ActiveMQ 5.6.0
> -------------------------------------------------------------------
>                 Key: AMQ-3836
>                 URL:
>             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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message