You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/05/02 00:38:16 UTC

[jira] [Commented] (AMQ-4493) Temporary destinations via STOMP fails using chained Request/Reply

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

Timothy Bish commented on AMQ-4493:
-----------------------------------

Recommend you try and create a Unit test based off what's already in the Stomp Unit tests to demonstrate the issue, then if something is fixed the test will protect the fix into the future. 
                
> Temporary destinations via STOMP fails using chained Request/Reply 
> -------------------------------------------------------------------
>
>                 Key: AMQ-4493
>                 URL: https://issues.apache.org/jira/browse/AMQ-4493
>             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: jms-request-reply.zip, 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: http://www.atlassian.com/software/jira