[jira] [Issue Comment Deleted] (ARTEMIS-3157) uneven number of connections in a cluster

["Erwin Dondorp (Jira)" <ji...@apache.org>]

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

Erwin Dondorp updated ARTEMIS-3157:
-----------------------------------
    Comment: was deleted

(was: relation with ARTEMIS-2870?

my answer: NO, ARTEMIS-2870 has been solved and the effect is still visible)

> uneven number of connections in a cluster
> -----------------------------------------
>
>                 Key: ARTEMIS-3157
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3157
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.17.0
>            Reporter: Erwin Dondorp
>            Priority: Minor
>
> Using a cluster of 3 master + 3 slave nodes. full interconnect, each with a fresh virtual disk.
> On each master nodes, the 2 static connections to the other master nodes are visible, and each is marked with the dedicated cluster username. so that part seems ok.
> but without any clients having connected, there are additional connections. the amount is not the same in each master node. Some connections show "127.0.0.1" as address, something that is not in my configuration. none of the extra connections have any sessions.
> the details of an example:
> * broker1: 3 connections to own slave; 2 extra to/from broker2; 1 extra to/from backup of broker3
> * broker2: 3 connections to own slave; 2 extra to/from broker1; 2 extra to/from broker3; 1 extra to/from slave of broker3
> * broker3: 1 connection to own slave; no other extra connections
> the exact amount of connections varies a little between startups and also seems to depend on the exact startup sequence.
> my assumption is that these connections should not be present, and that this is not intended, hence this report. my wild guess is that these are remnants from connections that did not success due to the cluster not fully available yet.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)