[ARTEMIS-1262] JMS 2.0 durable subscription spec violation

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.1.0
• Component/s: Broker
• Assignee: Unassigned
• Reporter: Christopher L. Shannon
• Created: 29/Jun/17 18:19
• Updated: 11/Apr/18 11:49

Description

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:

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.

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.