[
https://issues.apache.org/jira/browse/ARTEMIS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575148#comment-16575148
]
Jeff Mesnil commented on ARTEMIS-1206:
--------------------------------------
JMS 2.0 spec, section 6.1.2. Client identifier
> The purpose of client identifier is to associate a connection and its objects
> with a state maintained on behalf of the client by a provider. By definition,
> the client state identified by a client identifier can be ‘in use’ by only
> one client at a time. A JMS provider must prevent concurrently executing
> clients from using it.
> [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
> Affects Versions: 2.1.0
> Reporter: Michael Andre Pearce
> Assignee: clebert suconic
> Priority: Major
> Fix For: 2.2.0
>
> 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
(v7.6.3#76005)
