[
https://issues.apache.org/jira/browse/ARTEMIS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039255#comment-16039255
]
ASF GitHub Bot commented on ARTEMIS-1206:
-----------------------------------------
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/1321
ARTEMIS-1206 SetClientID from Core ConnectionFactory is not unique
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis ARTEMIS-1206
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1321.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1321
----
commit 8368f410436e68a48b53213ea5a98f5b82f3b00d
Author: Clebert Suconic <clebertsuco...@apache.org>
Date: 2017-06-06T16:58:28Z
ARTEMIS-1206 SetClientID from Core ConnectionFactory is not unique
----
> [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)
