[
https://issues.apache.org/jira/browse/ARTEMIS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038910#comment-16038910
]
Robbie Gemmell commented on ARTEMIS-1206:
-----------------------------------------
{quote}
However, since the use-case here is a client using the JMS API with multiple
different implementations it was clear he should be using the JMS API strictly
rather than implementation-specific methods. We'll still want to fix setting
the clientID via the connection factory.
{quote}
Yep, or using JNDI for the ConnectionFactory also works to remove need for any
implementation-specific methods. I didnt see the IRC conversation, so I'm
unclear if that shows the same behaviour as the factory setter or not. Either
way, I'd agree it should be fixed and so would reopen the JIRA for that (I dont
have the necessary JIRA project permissions or I'd do it).
The main use case I've seen for Connection#setClientID was only if you somehow
need to use a single ConnectionFactory for creating multiple [concurrent]
connections with different ClientID's, or since JMS 2.0 also some with ClientID
and some without.
> [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)
