You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Jan-Helge Bergesen (JIRA)" <ji...@apache.org> on 2013/04/29 10:04:15 UTC

[jira] [Updated] (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:all-tabpanel ]

Jan-Helge Bergesen updated AMQ-4493:
------------------------------------

    Attachment: jms-request-reply.zip

Test-setup with 3 applications.
ZIP file contains powerpoint summary, as well as STOMP on-wire tracing.
                
> 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: Standalone application, 2 Camel XML apps (2.10.3), ActiveMQ vanilla install (5.8.0)
>            Reporter: Jan-Helge Bergesen
>         Attachments: jms-request-reply.zip
>
>
> 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