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

Robbie Gemmell commented on ARTEMIS-1206:
-----------------------------------------

I still believe the ClientID is per-Connection, not per-ConnectionFactory. I 
dont see that the the latter is really implied or stated, whereas the former is 
implied and stated in the Javadoc and there are certainly references to that 
behaviour within the JMS spec process itself, e.g such as the work adding 
shared subscriptions noting that if a ClientID is set you can only share that 
subscription on a single connection as only one connection can use the ClientID 
at a time. I dont read from the spec that restrictions on duplicate ClientIDs 
only applies to uses of setClientID, but rather the restriction is on the value 
of ClientIDs in use on any connection and not just those which called 
setClientID.

I have no issue with for example making it configurable so uses where there are 
extenuating circumstances, and perhaps when used within an RA it could be 
considerd different given JMS in general acts differently there, but I think 
the current behaviour is the correct for the standalone client.

> [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)

Reply via email to