[
https://issues.apache.org/jira/browse/ARTEMIS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576018#comment-16576018
]
Robbie Gemmell commented on ARTEMIS-1206:
-----------------------------------------
{quote}Where is it written?
{quote}
It is written in a section you quoted above, where you aren't allowed to set a
ClientID if it is in use by another connection, and written/implied by the
other statement you quoted where concurrent use of the ClientID state must be
prevented, and implied by the singular description of transparently applying an
administratively-configured ClientID to the connection.
{quote}Which ones? I did not find any other mention of the ClientID that was is
already in the Connection.setClientID() javadoc.
{quote}
The references I referred to were part of the spec process in JMS 2, not
additional mentions in the spec itself. I think thats reasonable since, to me
and others, it already outlines the behaviour elsewhere (though poorly I would
agree) and needn't repeat it.
The behaviour was mentioned here when adding shared subscriptions:
[https://github.com/eclipse-ee4j/jms-api/issues/40]
And also mentioned here when making ClientID optional for them (both issues
really part of the same change in my mind):
[https://github.com/eclipse-ee4j/jms-api/issues/39]
There may be others, I just recall these because when implementing shared subs
I thought to myself 'doesnt this mean it is only sharable on a single
connection when a ClientID is set', and reading the spec discussions and JIRAs
(at the time, now GitHub issues) for the additions found they stated that is
the case.
{quote}Where do you read that?
{quote}
Everywhere previously discussed reads that way to me.
> [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)
