Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9D29A200B21 for ; Fri, 10 Jun 2016 20:10:18 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9BC60160A38; Fri, 10 Jun 2016 18:10:18 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 15804160A15 for ; Fri, 10 Jun 2016 20:10:17 +0200 (CEST) Received: (qmail 25845 invoked by uid 500); 10 Jun 2016 18:10:17 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Delivered-To: moderator for users@activemq.apache.org Received: (qmail 20526 invoked by uid 99); 10 Jun 2016 17:17:42 -0000 X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.8 X-Spam-Level: *** X-Spam-Status: No, score=3.8 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_ENVFROM_END_DIGIT=0.25, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313, URI_TRY_3LD=0.064] autolearn=disabled Date: Fri, 10 Jun 2016 09:38:52 -0700 (PDT) From: aanto To: users@activemq.apache.org Message-ID: <1465576732833-4712878.post@n4.nabble.com> In-Reply-To: <571109CD.7010703@gmail.com> References: <1460573732997-4710740.post@n4.nabble.com> <570ECEA1.6050108@gmail.com> <1460665247892-4710790.post@n4.nabble.com> <571109CD.7010703@gmail.com> Subject: Re: ActiveMQ 5.13.0 - Bug in Composite Destination using Stomp ? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Fri, 10 Jun 2016 18:10:18 -0000 This bug fix seems to be a partial fix, which was part of 5.13.3. stompconnection.send("queue://test.aanto1.queue,topic://test.aanto2.topic", "messsage1", "tx1", null); => PASS: creates QUEUE "test.aanto1.queue" => FAIL: creates QUEUE "topic://test.aanto2.topic", instead of creating a TOPIC "test.aanto2.topic" stompconnection.send("test.aanto1.queue,queue://test.aanto2.queue", "messsage1", "tx1", null); => PASS: creates QUEUE "test.aanto1.queue" => FAIL: creates QUEUE "queue://test.aanto2.queue", instead of creating a QUEUE "test.aanto2.queue" stompconnection.send("topic://test.aanto1.topic,topic://test.aanto2.topic", "messsage1", "tx1", null); => PASS: creates TOPIC "test.aanto1.topic" => FAIL: creates QUEUE "topic://test.aanto2.topic", instead of creating a TOPIC "test.aanto2.topic" Thank you Aanto. -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-13-0-Bug-in-Composite-Destination-using-Stomp-tp4710740p4712878.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.