Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 5 Jun 2017 20:52:04 +0000 (UTC)
From: "Michael Andre Pearce (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.13077267.1496677116000.368742.1496695924478@Atlassian.JIRA>
In-Reply-To: <JIRA.13077267.1496677116000@Atlassian.JIRA>
References: <JIRA.13077267.1496677116000@Atlassian.JIRA> <JIRA.13077267.1496677116650@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (ARTEMIS-1206) [Core JMS Client] Violates JMS
 Specification - allows two active connections with same clientid
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 05 Jun 2017 20:52:11 -0000


     [ https://issues.apache.org/jira/browse/ARTEMIS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Andre Pearce resolved ARTEMIS-1206.
-------------------------------------------
    Resolution: Invalid

This is invalid, as discussed on IRC, the test was setting the client id in the CF, on moving this to setting it on the connection via JMS API, there still is a difference in behaviour of when it is valid to be able to set clientId though it seems the behaviour isn't clear in JMS spec, where QPID and ActiveMQ5 allow you to set an exception listener first, where as currently Artemis requires the very first call to setClientId if you wish to set it. 

As discussed will create and align the clients so even so not detailed in spec, a user of ActiveMQ5 client or QPID client can expect the same behaviour.

> [Core JMS Client] Violates JMS Specification - allows two active connections with same clientid
> -----------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1206
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1206
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Michael Andre Pearce
>         Attachments: JMSDurableConsumerTest2.java, JMSDurableConsumerTest2.java
>
>
> Currently it is possible to make two completely separate client connections to the broker, with the same client id.
> This was found/raised as a possible bug in Core Client on looking at differing behaviours between the Core JMS Client and the Qpid AMQP Client.
> https://issues.apache.org/jira/browse/ARTEMIS-1205
> Attached is a test case, where by the Qpid Client errors, and the Core Client does not, executing the same client code.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)