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 Mon, 05 Jun 2017 16:05:04 GMT

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

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

There are multiple places its referenced, e.g the above, or also: http://docs.oracle.com/javaee/7/api/javax/jms/Connection.html#setClientID-java.lang.String-
{quote}
If another connection with the same clientID is already running when this method is called,
the JMS provider should detect the duplicate ID and throw an InvalidClientIDException.
{quote}

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