Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 29 Jun 2017 19:43:00 +0000 (UTC)
From: "Christopher L. Shannon (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.13083543.1498760399000.137640.1498765380369@Atlassian.JIRA>
In-Reply-To: <JIRA.13083543.1498760399000@Atlassian.JIRA>
References: <JIRA.13083543.1498760399000@Atlassian.JIRA> <JIRA.13083543.1498760399446@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ARTEMIS-1262) JMS 2.0 durable subscription spec
 violation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 29 Jun 2017 19:43:12 -0000


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

Christopher L. Shannon commented on ARTEMIS-1262:
-------------------------------------------------

I think you may be misreading it or mixing up shared non-durable versus shared durable.  In this case, yes a shared non-durable consumer is separate from a shared durable subscription and the subscriptions are different.

However in the case of non-shared durable subscriptions and shared durable subscriptions there is a restriction.  The javadoc you linked says:

"A shared durable subscription and an unshared durable subscription may not have the same name and client identifier (if set). If an unshared durable subscription already exists with the same name and client identifier (if set) then a JMSRuntimeException is thrown."

So an exception needs to be thrown.

> JMS 2.0 durable subscription spec violation
> -------------------------------------------
>
>                 Key: ARTEMIS-1262
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1262
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.1.0
>            Reporter: Christopher L. Shannon
>
> There is a JMS 2.0 spec violation with Artemis.  Currently it is possible to first create a durable subscription with a clientId and subscription name and then also create a shared durable subscription using the same clientId and subscription name.  This works because Artemis isn't distinguishing between the two types of consumers during the creation of the consumer.  However, the spec says:
> {quote}A shared durable subscription and an unshared durable subscription may not
> have the same name and client identifier. If the application calls one of the
> createSharedDurableConsumer methods, and an unshared durable 
> subscription already exists with the same name and client identifier, then a
> JMSException or JMSRuntimeException is thrown.{quote}
> I think that there may need to be a flag added somewhere during the creation of the consumer so the broker can tell whether or not the durable subscription is shared vs non-shared so it can reject a shared subscription attempt if a non-shared subscription exists for the same client Id and name.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)