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 B388D200C8E for ; Thu, 8 Jun 2017 15:08:38 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B2362160BD5; Thu, 8 Jun 2017 13:08:38 +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 EFF87160BCA for ; Thu, 8 Jun 2017 15:08:37 +0200 (CEST) Received: (qmail 83960 invoked by uid 500); 8 Jun 2017 13:08:37 -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 83949 invoked by uid 99); 8 Jun 2017 13:08:36 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jun 2017 13:08:36 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id BD8EBDFE61; Thu, 8 Jun 2017 13:08:36 +0000 (UTC) From: michaelandrepearce To: dev@activemq.apache.org Reply-To: dev@activemq.apache.org References: In-Reply-To: Subject: [GitHub] activemq-artemis issue #1325: ARTEMIS-1205: AMQP Shared Durable Subscriber i... Content-Type: text/plain Message-Id: <20170608130836.BD8EBDFE61@git1-us-west.apache.org> Date: Thu, 8 Jun 2017 13:08:36 +0000 (UTC) archived-at: Thu, 08 Jun 2017 13:08:38 -0000 Github user michaelandrepearce commented on the issue: https://github.com/apache/activemq-artemis/pull/1325 On further testing we discovered that core escapes these, as such rather than changing core behaviour which has been working as such has active users, changed the AMQP behaviour, to match core. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---