activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARTEMIS-1206) [Core JMS Client] Violates JMS Specification - allows two active connections with same clientid
Date Mon, 05 Jun 2017 15:44:04 GMT

     [ https://issues.apache.org/jira/browse/ARTEMIS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish updated ARTEMIS-1206:
----------------------------------
    Summary: [Core JMS Client] Violates JMS Specification - allows two active connections
with same clientid  (was: [Core JMS Client] Violates JMS 2.0 Specification - allows two active
connections with same clientid)

> [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 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, where as the Core Client does
not.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message