activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-4493) Temporary destinations via STOMP fails using chained Request/Reply
Date Thu, 02 May 2013 13:58:16 GMT


Timothy Bish commented on AMQ-4493:

If its an issue with StompJMS then it should be tracked there, if its an ActiveMQ issue the
test will need to be translated into a JUnit test that uses the style in activemq-stomp/src/test
so that we can include it for future testing.  If you want to give that a shot we'd appreciate
it otherwise it'll have to wait until someone has a chance to work on it.  Thanks. 
> Temporary destinations via STOMP fails using chained Request/Reply 
> -------------------------------------------------------------------
>                 Key: AMQ-4493
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, stomp
>    Affects Versions: 5.8.0
>         Environment: 1 x Standalone application, 2 x Camel XML apps (2.10.3), ActiveMQ
vanilla install (5.8.0).
> Run on Windows 7, but also with broker run on Red Hat Enterprise Linux Server release
6.3 (Santiago)
>            Reporter: Jan-Helge Bergesen
>         Attachments:, observation.png
> It may seem like the conversion between STOMP temporary destination names (i.e /temp-queue/xx
+ /temp-topic/xx) to exposed internal representation (i.e /remote-temp-queue/ID\:xxxxx) fails
under certain conditions.
> Will attach test setup that demonstrates behavior, both on 5.8.0 and 5.7.0.

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

View raw message