[jira] [Commented] (AMQ-9197) Prototype Javascript Framework - CVE-2020-27511
[ https://issues.apache.org/jira/browse/AMQ-9197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684471#comment-17684471 ] Nikhil commented on AMQ-9197: - Hi [~jbonofre] Looks like the vulnerable code exists in older versions as well through *1.6.x* which is part of ActiveMQ library.. this is fixed in *1.7.1-3* version of prototype.js module.. Could you please review once ? Reference - [https://security-tracker.debian.org/tracker/CVE-2020-27511] Thank you! > Prototype Javascript Framework - CVE-2020-27511 > --- > > Key: AMQ-9197 > URL: https://issues.apache.org/jira/browse/AMQ-9197 > Project: ActiveMQ > Issue Type: Dependency upgrade > Components: Web Console >Affects Versions: 5.16.3, 5.16.4, 5.16.5 >Reporter: Nikhil >Assignee: Jean-Baptiste Onofré >Priority: Major > > An issue was discovered in the stripTags and unescapeHTML components in > Prototype 1.7.3 version 1.6 and below where an attacker can cause a Regular > Expression Denial of Service (ReDOS) through stripping crafted HTML tags. > > See [https://nvd.nist.gov/vuln/detail/CVE-2020-27511] for further details > > *prototype.js* is part of activemq-web-5.16.3.jar which is shipped inside > *activemq-web-console.war* > > Can someone please confirm the affected projects of activeMQ for this > prototype.js library.. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (AMQ-9197) Prototype Javascript Framework - CVE-2020-27511
[ https://issues.apache.org/jira/browse/AMQ-9197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil reopened AMQ-9197: - > Prototype Javascript Framework - CVE-2020-27511 > --- > > Key: AMQ-9197 > URL: https://issues.apache.org/jira/browse/AMQ-9197 > Project: ActiveMQ > Issue Type: Dependency upgrade > Components: Web Console >Affects Versions: 5.16.3, 5.16.4, 5.16.5 >Reporter: Nikhil >Assignee: Jean-Baptiste Onofré >Priority: Major > > An issue was discovered in the stripTags and unescapeHTML components in > Prototype 1.7.3 version 1.6 and below where an attacker can cause a Regular > Expression Denial of Service (ReDOS) through stripping crafted HTML tags. > > See [https://nvd.nist.gov/vuln/detail/CVE-2020-27511] for further details > > *prototype.js* is part of activemq-web-5.16.3.jar which is shipped inside > *activemq-web-console.war* > > Can someone please confirm the affected projects of activeMQ for this > prototype.js library.. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[
https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684427#comment-17684427
]
Justin Bertram edited comment on ARTEMIS-4156 at 2/6/23 5:27 AM:
-
You haven't provided any details about the plugin you've deployed. Generally
speaking, if the broker works fine without a plugin and then breaks after
deploying the plugin then the likely source of the problem is the plugin itself.
Please provide a way to reproduce what you're observing.
Also, please attach your {{management.xml}} and provide details of what user &
role you're logging into the console with.
was (Author: jbertram):
Also, you haven't provided any details about the plugin you've deployed.
Generally speaking, if the broker works fine without a plugin and then breaks
after deploying the plugin then the likely source of the problem is the plugin
itself.
Please provide a way to reproduce what you're observing.
> could not invoke list connectionsjava.lang.Exception : User not authorized to
> access operation: listConnections
> ---
>
> Key: ARTEMIS-4156
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4156
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.26.0, 2.27.1
>Reporter: gongping.zhu
>Priority: Major
> Attachments: image-2023-02-06-11-52-29-213.png
>
>
> When I deploy the plugin developed using spring-related components to
> artemis, the system can perform authentication and authentication normally,
> and can authenticate clientId normally, but its management console cannot be
> used normally, and an error message of no permission is always reported, such
> as: could not invoke list connectionsjava.lang.Exception: User not authorized
> to access operation: listConnections
> !image-2023-02-06-11-52-29-213.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[ https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-4156: Description: When I deploy the plugin developed using spring-related components to artemis, the system can perform authentication and authentication normally, and can authenticate clientId normally, but its management console cannot be used normally, and an error message of no permission is always reported, such as: could not invoke list connectionsjava.lang.Exception: User not authorized to access operation: listConnections !image-2023-02-06-11-52-29-213.png! was: When I deploy the plugin developed using spring-related components to artemis, the system can perform authentication and authentication normally, and can authenticate clientId normally, but its management console cannot be used normally, and an error message of no permission is always reported, such as: could not invoke list connectionsjava.lang.Exception: User not authorized to access operation: listConnections !image-2023-02-06-11-52-29-213.png|thumbnail, width=300,height=400! > could not invoke list connectionsjava.lang.Exception : User not authorized to > access operation: listConnections > --- > > Key: ARTEMIS-4156 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0, 2.27.1 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-02-06-11-52-29-213.png > > > When I deploy the plugin developed using spring-related components to > artemis, the system can perform authentication and authentication normally, > and can authenticate clientId normally, but its management console cannot be > used normally, and an error message of no permission is always reported, such > as: could not invoke list connectionsjava.lang.Exception: User not authorized > to access operation: listConnections > !image-2023-02-06-11-52-29-213.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[ https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-4156: Description: When I deploy the plugin developed using spring-related components to artemis, the system can perform authentication and authentication normally, and can authenticate clientId normally, but its management console cannot be used normally, and an error message of no permission is always reported, such as: could not invoke list connectionsjava.lang.Exception: User not authorized to access operation: listConnections !image-2023-02-06-11-52-29-213.png|thumbnail, width=300,height=400! was: When I deploy the plugin developed using spring-related components to artemis, the system can perform authentication and authentication normally, and can authenticate clientId normally, but its management console cannot be used normally, and an error message of no permission is always reported, such as: could not invoke list connectionsjava.lang.Exception: User not authorized to access operation: listConnections !image-2023-02-06-11-52-29-213.png|thumbnail! > could not invoke list connectionsjava.lang.Exception : User not authorized to > access operation: listConnections > --- > > Key: ARTEMIS-4156 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0, 2.27.1 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-02-06-11-52-29-213.png > > > When I deploy the plugin developed using spring-related components to > artemis, the system can perform authentication and authentication normally, > and can authenticate clientId normally, but its management console cannot be > used normally, and an error message of no permission is always reported, such > as: could not invoke list connectionsjava.lang.Exception: User not authorized > to access operation: listConnections > !image-2023-02-06-11-52-29-213.png|thumbnail, width=300,height=400! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[ https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-4156: Description: When I deploy the plugin developed using spring-related components to artemis, the system can perform authentication and authentication normally, and can authenticate clientId normally, but its management console cannot be used normally, and an error message of no permission is always reported, such as: could not invoke list connectionsjava.lang.Exception: User not authorized to access operation: listConnections !image-2023-02-06-11-52-29-213.png|thumbnail! was: When I deploy the plugin developed using spring-related components to artemis, the system can perform authentication and authentication normally, and can authenticate clientId normally, but its management console cannot be used normally, and an error message of no permission is always reported, such as: could not invoke list connectionsjava.lang.Exception: User not authorized to access operation: listConnections !image-2023-02-06-11-52-29-213.png! > could not invoke list connectionsjava.lang.Exception : User not authorized to > access operation: listConnections > --- > > Key: ARTEMIS-4156 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0, 2.27.1 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-02-06-11-52-29-213.png > > > When I deploy the plugin developed using spring-related components to > artemis, the system can perform authentication and authentication normally, > and can authenticate clientId normally, but its management console cannot be > used normally, and an error message of no permission is always reported, such > as: could not invoke list connectionsjava.lang.Exception: User not authorized > to access operation: listConnections > !image-2023-02-06-11-52-29-213.png|thumbnail! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[ https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684427#comment-17684427 ] Justin Bertram edited comment on ARTEMIS-4156 at 2/6/23 5:22 AM: - Also, you haven't provided any details about the plugin you've deployed. Generally speaking, if the broker works fine without a plugin and then breaks after deploying the plugin then the likely source of the problem is the plugin itself. Please provide a way to reproduce what you're observing. was (Author: jbertram): I don't see a message about authorization failure in the screenshot you attached. Also, you haven't provided any details about the plugin you've deployed. Generally speaking, if the broker works fine without a plugin and then breaks after deploying the plugin then the likely source of the problem is the plugin itself. Please provide a way to reproduce what you're observing. > could not invoke list connectionsjava.lang.Exception : User not authorized to > access operation: listConnections > --- > > Key: ARTEMIS-4156 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0, 2.27.1 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-02-06-11-52-29-213.png > > > When I deploy the plugin developed using spring-related components to > artemis, the system can perform authentication and authentication normally, > and can authenticate clientId normally, but its management console cannot be > used normally, and an error message of no permission is always reported, such > as: could not invoke list connectionsjava.lang.Exception: User not authorized > to access operation: listConnections > !image-2023-02-06-11-52-29-213.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[ https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684427#comment-17684427 ] Justin Bertram commented on ARTEMIS-4156: - I don't see a message about authorization failure in the screenshot you attached. Also, you haven't provided any details about the plugin you've deployed. Generally speaking, if the broker works fine without a plugin and then breaks after deploying the plugin then the likely source of the problem is the plugin itself. Please provide a way to reproduce what you're observing. > could not invoke list connectionsjava.lang.Exception : User not authorized to > access operation: listConnections > --- > > Key: ARTEMIS-4156 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0, 2.27.1 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-02-06-11-52-29-213.png > > > When I deploy the plugin developed using spring-related components to > artemis, the system can perform authentication and authentication normally, > and can authenticate clientId normally, but its management console cannot be > used normally, and an error message of no permission is always reported, such > as: could not invoke list connectionsjava.lang.Exception: User not authorized > to access operation: listConnections > !image-2023-02-06-11-52-29-213.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[ https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-4156: Description: When I deploy the plugin developed using spring-related components to artemis, the system can perform authentication and authentication normally, and can authenticate clientId normally, but its management console cannot be used normally, and an error message of no permission is always reported, such as: could not invoke list connectionsjava.lang.Exception: User not authorized to access operation: listConnections !image-2023-02-06-11-52-29-213.png! was:!image-2023-02-06-11-52-29-213.png! > could not invoke list connectionsjava.lang.Exception : User not authorized to > access operation: listConnections > --- > > Key: ARTEMIS-4156 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0, 2.27.1 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-02-06-11-52-29-213.png > > > When I deploy the plugin developed using spring-related components to > artemis, the system can perform authentication and authentication normally, > and can authenticate clientId normally, but its management console cannot be > used normally, and an error message of no permission is always reported, such > as: could not invoke list connectionsjava.lang.Exception: User not authorized > to access operation: listConnections > !image-2023-02-06-11-52-29-213.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[ https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-4156: Environment: (was: When I deploy the plugin developed using spring-related components to artemis, the system can perform authentication and authentication normally, and can authenticate clientId normally, but its management console cannot be used normally, and an error message of no permission is always reported, such as: could not invoke list connectionsjava.lang.Exception: User not authorized to access operation: listConnections) > could not invoke list connectionsjava.lang.Exception : User not authorized to > access operation: listConnections > --- > > Key: ARTEMIS-4156 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0, 2.27.1 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-02-06-11-52-29-213.png > > > !image-2023-02-06-11-52-29-213.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[ https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-4156: -- Affects Version/s: 2.27.1 > could not invoke list connectionsjava.lang.Exception : User not authorized to > access operation: listConnections > --- > > Key: ARTEMIS-4156 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0, 2.27.1 > Environment: When I deploy the plugin developed using spring-related > components to artemis, the system can perform authentication and > authentication normally, and can authenticate clientId normally, but its > management console cannot be used normally, and an error message of no > permission is always reported, such as: could not invoke list > connectionsjava.lang.Exception: User not authorized to access operation: > listConnections >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-02-06-11-52-29-213.png > > > !image-2023-02-06-11-52-29-213.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[ https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-4156: -- Environment: When I deploy the plugin developed using spring-related components to artemis, the system can perform authentication and authentication normally, and can authenticate clientId normally, but its management console cannot be used normally, and an error message of no permission is always reported, such as: could not invoke list connectionsjava.lang.Exception: User not authorized to access operation: listConnections (was: When I deploy the developed plugin to artemis, the system can perform authentication and authentication normally, and the clientId can be authenticated normally, but its management console cannot be used normally, and it keeps reporting an error message that there is no permission, such as: could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections) > could not invoke list connectionsjava.lang.Exception : User not authorized to > access operation: listConnections > --- > > Key: ARTEMIS-4156 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0 > Environment: When I deploy the plugin developed using spring-related > components to artemis, the system can perform authentication and > authentication normally, and can authenticate clientId normally, but its > management console cannot be used normally, and an error message of no > permission is always reported, such as: could not invoke list > connectionsjava.lang.Exception: User not authorized to access operation: > listConnections >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-02-06-11-52-29-213.png > > > !image-2023-02-06-11-52-29-213.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
gongping.zhu created ARTEMIS-4156: - Summary: could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections Key: ARTEMIS-4156 URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.26.0 Environment: When I deploy the developed plugin to artemis, the system can perform authentication and authentication normally, and the clientId can be authenticated normally, but its management console cannot be used normally, and it keeps reporting an error message that there is no permission, such as: could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections Reporter: gongping.zhu Attachments: image-2023-02-06-11-52-29-213.png !image-2023-02-06-11-52-29-213.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3157) uneven number of connections in a cluster
[ https://issues.apache.org/jira/browse/ARTEMIS-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwin Dondorp updated ARTEMIS-3157: --- Attachment: (was: screenshot-3.png) > 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: Major > Attachments: image-2023-02-05-12-59-48-929.png, > image-2023-02-05-12-59-55-732.png, screenshot-1.png > > > Using a cluster of 3 master + 3 slave nodes. full interconnect, each with a > fresh virtual disk. no other constructions > (bridges/federation/brokerconn/etc) and also no clients. > 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. Also the connections do not 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 succeed due to the other cluster-members not > fully available yet. > When the cluster is started one node at a time, the effect seems to exists > only on the first node that was started. > Note: not related to ARTEMIS-2870 as this report is still valid in > 2.18.0-20210322.234647-43. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3157) uneven number of connections in a cluster
[ https://issues.apache.org/jira/browse/ARTEMIS-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwin Dondorp updated ARTEMIS-3157: --- Attachment: (was: screenshot-2.png) > 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: Major > Attachments: image-2023-02-05-12-59-48-929.png, > image-2023-02-05-12-59-55-732.png, screenshot-1.png > > > Using a cluster of 3 master + 3 slave nodes. full interconnect, each with a > fresh virtual disk. no other constructions > (bridges/federation/brokerconn/etc) and also no clients. > 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. Also the connections do not 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 succeed due to the other cluster-members not > fully available yet. > When the cluster is started one node at a time, the effect seems to exists > only on the first node that was started. > Note: not related to ARTEMIS-2870 as this report is still valid in > 2.18.0-20210322.234647-43. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3157) uneven number of connections in a cluster
[
https://issues.apache.org/jira/browse/ARTEMIS-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684284#comment-17684284
]
Erwin Dondorp edited comment on ARTEMIS-3157 at 2/5/23 12:00 PM:
-
> Can you reproduce this on a simpler configuration (e.g. 2 live brokers, no
> backups)?
and then I responded with an even more complicated example... :-( sorry!
but I'm still looking to have the list of connections that we see explained.
the setup is now a cluster with just 2 nodes, each having a static connector to
the other node.
there are no regular clients involved.
in this case, both nodes show roughly the same list of connections. see the
pictures below.
there is 1 cluster connection that I understand, it has the expected username
and it has a non-zero session count.
but the other 2 connections are a puzzle to me.
so the questions are: should these 2 connections be present, and if so, what
are they for?
{panel:title=connections in cluster node 1}
!image-2023-02-05-12-59-48-929.png!
{panel}
{panel:title=connections in cluster node 2}
!image-2023-02-05-12-59-55-732.png!
{panel}
was (Author: erwindon):
> Can you reproduce this on a simpler configuration (e.g. 2 live brokers, no
> backups)?
and then I responded with an even more complicated example... :-( sorry!
but I'm still looking to have the list of connections that we see explained.
the setup is now a cluster with just 2 nodes, each having a static connector to
the other node.
there are no regular clients involved.
in this case, both nodes show roughly the same list of connections. see the
pictures below.
there is 1 cluster connection that I understand, it has the expected username
and it has a non-zero session count.
but the other 2 connections are a puzzle to me.
so the questions are: should these 2 connections be present, and if so, what
are they for?
{panel:title=connections in cluster node 1}
!screenshot-2.png!
{panel}
{panel:title=connections in cluster node 2}
!screenshot-3.png!
{panel}
> 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: Major
> Attachments: image-2023-02-05-12-59-48-929.png,
> image-2023-02-05-12-59-55-732.png, screenshot-1.png, screenshot-2.png,
> screenshot-3.png
>
>
> Using a cluster of 3 master + 3 slave nodes. full interconnect, each with a
> fresh virtual disk. no other constructions
> (bridges/federation/brokerconn/etc) and also no clients.
> 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. Also the connections do not 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 succeed due to the other cluster-members not
> fully available yet.
> When the cluster is started one node at a time, the effect seems to exists
> only on the first node that was started.
> Note: not related to ARTEMIS-2870 as this report is still valid in
> 2.18.0-20210322.234647-43.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3157) uneven number of connections in a cluster
[
https://issues.apache.org/jira/browse/ARTEMIS-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684284#comment-17684284
]
Erwin Dondorp commented on ARTEMIS-3157:
> Can you reproduce this on a simpler configuration (e.g. 2 live brokers, no
> backups)?
and then I responded with an even more complicated example... :-( sorry!
but I'm still looking to have the list of connections that we see explained.
the setup is now a cluster with just 2 nodes, each having a static connector to
the other node.
there are no regular clients involved.
in this case, both nodes show roughly the same list of connections. see the
pictures below.
there is 1 cluster connection that I understand, it has the expected username
and it has a non-zero session count.
but the other 2 connections are a puzzle to me.
so the questions are: should these 2 connections be present, and if so, what
are they for?
{panel:title=connections in cluster node 1}
!screenshot-2.png!
{panel}
{panel:title=connections in cluster node 2}
!screenshot-3.png!
{panel}
> 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: Major
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Using a cluster of 3 master + 3 slave nodes. full interconnect, each with a
> fresh virtual disk. no other constructions
> (bridges/federation/brokerconn/etc) and also no clients.
> 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. Also the connections do not 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 succeed due to the other cluster-members not
> fully available yet.
> When the cluster is started one node at a time, the effect seems to exists
> only on the first node that was started.
> Note: not related to ARTEMIS-2870 as this report is still valid in
> 2.18.0-20210322.234647-43.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3157) uneven number of connections in a cluster
[ https://issues.apache.org/jira/browse/ARTEMIS-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwin Dondorp updated ARTEMIS-3157: --- Attachment: screenshot-3.png > 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: Major > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > > Using a cluster of 3 master + 3 slave nodes. full interconnect, each with a > fresh virtual disk. no other constructions > (bridges/federation/brokerconn/etc) and also no clients. > 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. Also the connections do not 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 succeed due to the other cluster-members not > fully available yet. > When the cluster is started one node at a time, the effect seems to exists > only on the first node that was started. > Note: not related to ARTEMIS-2870 as this report is still valid in > 2.18.0-20210322.234647-43. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3157) uneven number of connections in a cluster
[ https://issues.apache.org/jira/browse/ARTEMIS-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwin Dondorp updated ARTEMIS-3157: --- Attachment: screenshot-2.png > 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: Major > Attachments: screenshot-1.png, screenshot-2.png > > > Using a cluster of 3 master + 3 slave nodes. full interconnect, each with a > fresh virtual disk. no other constructions > (bridges/federation/brokerconn/etc) and also no clients. > 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. Also the connections do not 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 succeed due to the other cluster-members not > fully available yet. > When the cluster is started one node at a time, the effect seems to exists > only on the first node that was started. > Note: not related to ARTEMIS-2870 as this report is still valid in > 2.18.0-20210322.234647-43. -- This message was sent by Atlassian Jira (v8.20.10#820010)
