You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/12 08:30:22 UTC
[jira] [Commented] (ARTEMIS-728) Broker doesn't support unique jms
client-id (qpid-jms client)
[ https://issues.apache.org/jira/browse/ARTEMIS-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15483494#comment-15483494 ]
ASF GitHub Bot commented on ARTEMIS-728:
----------------------------------------
GitHub user gaohoward opened a pull request:
https://github.com/apache/activemq-artemis/pull/769
ARTEMIS-728 Broker doesn't support unique jms client-id (qpid-jms client)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gaohoward/activemq-artemis master-tck
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/769.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #769
----
commit 69cb9e0a2263d3d766bd664894c553c2bf99414e
Author: Howard Gao <ho...@gmail.com>
Date: 2016-09-12T08:27:11Z
ARTEMIS-728 Broker doesn't support unique jms client-id (qpid-jms client)
----
> Broker doesn't support unique jms client-id (qpid-jms client)
> -------------------------------------------------------------
>
> Key: ARTEMIS-728
> URL: https://issues.apache.org/jira/browse/ARTEMIS-728
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 1.3.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Fix For: 1.4.0
>
>
> Using qpid-jms client to set a client-id that has already set on another connection does't get expected InvalidClientIDException exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)