activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1206) [Core JMS Client] Violates JMS Specification - allows two active connections with same clientid
Date Tue, 06 Jun 2017 16:13:18 GMT

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

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

Yeah, if you used the setter on the CF impl (as above, not sure if its different with URIs
or via JNDI) then two connections succeed in using the same ClientID, whereas if you call
setClientID on an already-created Connection the second call will throw an exception (I dont
know what happens if you ignore the exception and continue anyway).

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

Mime
View raw message