[ https://issues.apache.org/jira/browse/ARTEMIS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039192#comment-16039192 ]
clebert suconic edited comment on ARTEMIS-1206 at 6/6/17 4:19 PM: ------------------------------------------------------------------ When I fixed this in HornetQ (whoa.. many years ago), I had used and developed what I called addUniqueMetadata... that method is not being used when creating a connection through the CF property. createConnectionInternal on ActiveMQConnectionFactory needs to also call the setClientID, and do some treatment to close the connection in case it failed. was (Author: clebertsuconic): When I fixed this in HornetQ (whoa.. many years ago), I had used and developed what I called addUniqueMetadata... that method is not being used when creating a connection... createConnectionInternal on ActiveMQConnectionFactory needs to also call the setClientID, and do some treatment to close the connection in case it failed. > [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)