Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 21E60103F9 for ; Mon, 29 Apr 2013 08:02:23 +0000 (UTC) Received: (qmail 16867 invoked by uid 500); 29 Apr 2013 08:02:22 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 15532 invoked by uid 500); 29 Apr 2013 08:02:18 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 15465 invoked by uid 99); 29 Apr 2013 08:02:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Apr 2013 08:02:16 +0000 Date: Mon, 29 Apr 2013 08:02:16 +0000 (UTC) From: "Jan-Helge Bergesen (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMQ-4493) Temporary destinations via STOMP fails using chained Request/Reply MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jan-Helge Bergesen created AMQ-4493: --------------------------------------- Summary: 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 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