You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Anusha R (JIRA)" <ji...@apache.org> on 2015/07/30 07:10:04 UTC
[jira] [Comment Edited] (AMQ-5210) Concurrent connections with same
clientid to network of brokers
[ https://issues.apache.org/jira/browse/AMQ-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647190#comment-14647190 ]
Anusha R edited comment on AMQ-5210 at 7/30/15 5:09 AM:
--------------------------------------------------------
Is anyone working on this issue.
Or anyone has idea, how to solve this issue.
Due to this issue, we are not able to use to activeMQ - network broker and finally we are not able to scale it
was (Author: anuravi):
Is anyone working on this issue.
Or anyone has idea, how to solve this issue.
> Concurrent connections with same clientid to network of brokers
> ---------------------------------------------------------------
>
> Key: AMQ-5210
> URL: https://issues.apache.org/jira/browse/AMQ-5210
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.9.1
> Environment: Linux
> Reporter: Paddy
>
> Two brokers A and B connected to each other as networks of brokers setup.
> Connect a client with clientid C1 to broker A.
> Case1: When another client with same client id (C1) is connected to broker A, it fails with exception ("already connected"), which is the expected behavior.
> Case2: When another client with same client id C1 is connected to broker B, it does not fail.
> Feature Request: Way to detect that there is an existing online connection with the same clientid in the network bridge so that "already connected" exception in Case2
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)