[jira] [Work logged] (ARTEMIS-4497) export summary on cluster-topology as metrics
[
https://issues.apache.org/jira/browse/ARTEMIS-4497?focusedWorklogId=890059=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-890059
]
ASF GitHub Bot logged work on ARTEMIS-4497:
---
Author: ASF GitHub Bot
Created on: 11/Nov/23 00:06
Start Date: 11/Nov/23 00:06
Worklog Time Spent: 10m
Work Description: erwindon opened a new pull request, #4668:
URL: https://github.com/apache/activemq-artemis/pull/4668
See https://issues.apache.org/jira/browse/ARTEMIS-4497
my design decision:
re-use the code from the implementation of {{listNetworkTopology}} and add
it separate to provide these metrics:
* artemis_cluster_lives_count
* artemis_cluster_backups_count
this is a bit of code duplication, but prevents risk of breaking a
refactored {{listNetworkTopology}}
Issue Time Tracking
---
Worklog Id: (was: 890059)
Remaining Estimate: 0h
Time Spent: 10m
> export summary on cluster-topology as metrics
> -
>
> Key: ARTEMIS-4497
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4497
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Clustering
>Affects Versions: 2.31.2
>Reporter: Erwin Dondorp
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The broker has functions to export metrics to a metrics-interface-provider
> (e.g. [https://github.com/rh-messaging/artemis-prometheus-metrics-plugin] for
> collection using REST).
> This is only a subset of what can be collected using the JMX interface. (and
> the JMX interface has real commands too).
> Information on the cluster-topology was not yet available in these metrics.
> Due to the numeric nature of the metrics, providing the full topology of the
> cluster (as JMX operation {{listNetworkTopology}} does) is not possible. But
> just providing the broker-count is already very valuable.
> the following 2 metrics can be exported:
> * artemis_cluster_lives_count
> * artemis_cluster_backups_count
> With this information available, administrators can be alerted about various
> issues in the cluster. Detailed analysis can be done using the JMX info
> and/or the Console.
> a PR has been added to add that information to the set of metrics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4497) export summary on cluster-topology as metrics
Erwin Dondorp created ARTEMIS-4497:
--
Summary: export summary on cluster-topology as metrics
Key: ARTEMIS-4497
URL: https://issues.apache.org/jira/browse/ARTEMIS-4497
Project: ActiveMQ Artemis
Issue Type: Improvement
Components: Clustering
Affects Versions: 2.31.2
Reporter: Erwin Dondorp
The broker has functions to export metrics to a metrics-interface-provider
(e.g. [https://github.com/rh-messaging/artemis-prometheus-metrics-plugin] for
collection using REST).
This is only a subset of what can be collected using the JMX interface. (and
the JMX interface has real commands too).
Information on the cluster-topology was not yet available in these metrics.
Due to the numeric nature of the metrics, providing the full topology of the
cluster (as JMX operation {{listNetworkTopology}} does) is not possible. But
just providing the broker-count is already very valuable.
the following 2 metrics can be exported:
* artemis_cluster_lives_count
* artemis_cluster_backups_count
With this information available, administrators can be alerted about various
issues in the cluster. Detailed analysis can be done using the JMX info and/or
the Console.
a PR has been added to add that information to the set of metrics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9385) Minor default JAAS realm cleanups
[ https://issues.apache.org/jira/browse/AMQ-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785020#comment-17785020 ] ASF subversion and git services commented on AMQ-9385: -- Commit 38262342f2a0c287d5a43f9ad00ca3b22aa401c0 in activemq's branch refs/heads/main from Matt Pavlovich [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=38262342f ] [AMQ-9385] Minor default jaas realm config clean-ups and documentation > Minor default JAAS realm cleanups > - > > Key: AMQ-9385 > URL: https://issues.apache.org/jira/browse/AMQ-9385 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 6.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > 1. jetty.xml should reference 'users' vs 'user' > 2. conf/groups.properties should have some doc on format for adding groups > and user members -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (AMQ-9385) Minor default JAAS realm cleanups
[ https://issues.apache.org/jira/browse/AMQ-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich closed AMQ-9385. --- Resolution: Fixed > Minor default JAAS realm cleanups > - > > Key: AMQ-9385 > URL: https://issues.apache.org/jira/browse/AMQ-9385 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 6.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > 1. jetty.xml should reference 'users' vs 'user' > 2. conf/groups.properties should have some doc on format for adding groups > and user members -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (AMQ-9385) Minor default JAAS realm cleanups
[ https://issues.apache.org/jira/browse/AMQ-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-9385 started by Matt Pavlovich. --- > Minor default JAAS realm cleanups > - > > Key: AMQ-9385 > URL: https://issues.apache.org/jira/browse/AMQ-9385 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 6.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > 1. jetty.xml should reference 'users' vs 'user' > 2. conf/groups.properties should have some doc on format for adding groups > and user members -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9385) Minor default JAAS realm cleanups
[ https://issues.apache.org/jira/browse/AMQ-9385?focusedWorklogId=889981=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-889981 ] ASF GitHub Bot logged work on AMQ-9385: --- Author: ASF GitHub Bot Created on: 10/Nov/23 17:24 Start Date: 10/Nov/23 17:24 Worklog Time Spent: 10m Work Description: mattrpav opened a new pull request, #1116: URL: https://github.com/apache/activemq/pull/1116 (no comment) Issue Time Tracking --- Worklog Id: (was: 889981) Remaining Estimate: 0h Time Spent: 10m > Minor default JAAS realm cleanups > - > > Key: AMQ-9385 > URL: https://issues.apache.org/jira/browse/AMQ-9385 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 6.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > 1. jetty.xml should reference 'users' vs 'user' > 2. conf/groups.properties should have some doc on format for adding groups > and user members -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9384) No authentication to access webconsole
[ https://issues.apache.org/jira/browse/AMQ-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785018#comment-17785018 ] ASF subversion and git services commented on AMQ-9384: -- Commit 6b4041b30651f0dcb6de7a86d3332a874df329d9 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=6b4041b30 ] Merge pull request #1115 from jbonofre/AMQ-9384 AMQ-9384: Fix "read" securityConstraint and authentication (including logout) > No authentication to access webconsole > -- > > Key: AMQ-9384 > URL: https://issues.apache.org/jira/browse/AMQ-9384 > Project: ActiveMQ > Issue Type: Bug > Components: Web Console >Affects Versions: 6.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > It seems that there's no authentication to access ActiveMQ admin/web console. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9384) No authentication to access webconsole
[ https://issues.apache.org/jira/browse/AMQ-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785017#comment-17785017 ] ASF subversion and git services commented on AMQ-9384: -- Commit 07d469287f419f9f8afe17bc1585073446b520d5 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=07d469287 ] AMQ-9384: Fix "read" securityConstraint and authentication (including logout) > No authentication to access webconsole > -- > > Key: AMQ-9384 > URL: https://issues.apache.org/jira/browse/AMQ-9384 > Project: ActiveMQ > Issue Type: Bug > Components: Web Console >Affects Versions: 6.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > It seems that there's no authentication to access ActiveMQ admin/web console. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9384) No authentication to access webconsole
[ https://issues.apache.org/jira/browse/AMQ-9384?focusedWorklogId=889980=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-889980 ] ASF GitHub Bot logged work on AMQ-9384: --- Author: ASF GitHub Bot Created on: 10/Nov/23 17:22 Start Date: 10/Nov/23 17:22 Worklog Time Spent: 10m Work Description: jbonofre merged PR #1115: URL: https://github.com/apache/activemq/pull/1115 Issue Time Tracking --- Worklog Id: (was: 889980) Time Spent: 20m (was: 10m) > No authentication to access webconsole > -- > > Key: AMQ-9384 > URL: https://issues.apache.org/jira/browse/AMQ-9384 > Project: ActiveMQ > Issue Type: Bug > Components: Web Console >Affects Versions: 6.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > It seems that there's no authentication to access ActiveMQ admin/web console. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (AMQ-9384) No authentication to access webconsole
[ https://issues.apache.org/jira/browse/AMQ-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-9384. --- Resolution: Fixed > No authentication to access webconsole > -- > > Key: AMQ-9384 > URL: https://issues.apache.org/jira/browse/AMQ-9384 > Project: ActiveMQ > Issue Type: Bug > Components: Web Console >Affects Versions: 6.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > It seems that there's no authentication to access ActiveMQ admin/web console. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (AMQ-9385) Minor default JAAS realm cleanups
[ https://issues.apache.org/jira/browse/AMQ-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-9385: --- Assignee: Matt Pavlovich > Minor default JAAS realm cleanups > - > > Key: AMQ-9385 > URL: https://issues.apache.org/jira/browse/AMQ-9385 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 6.0.0 > > > 1. jetty.xml should reference 'users' vs 'user' > 2. conf/groups.properties should have some doc on format for adding groups > and user members -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9385) Minor default JAAS realm cleanups
[ https://issues.apache.org/jira/browse/AMQ-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-9385: Fix Version/s: 6.0.0 > Minor default JAAS realm cleanups > - > > Key: AMQ-9385 > URL: https://issues.apache.org/jira/browse/AMQ-9385 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Priority: Minor > Fix For: 6.0.0 > > > 1. jetty.xml should reference 'users' vs 'user' > 2. conf/groups.properties should have some doc on format for adding groups > and user members -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (AMQ-9385) Minor default JAAS realm cleanups
Matt Pavlovich created AMQ-9385: --- Summary: Minor default JAAS realm cleanups Key: AMQ-9385 URL: https://issues.apache.org/jira/browse/AMQ-9385 Project: ActiveMQ Issue Type: Task Reporter: Matt Pavlovich 1. jetty.xml should reference 'users' vs 'user' 2. conf/groups.properties should have some doc on format for adding groups and user members -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9384) No authentication to access webconsole
[ https://issues.apache.org/jira/browse/AMQ-9384?focusedWorklogId=889976=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-889976 ] ASF GitHub Bot logged work on AMQ-9384: --- Author: ASF GitHub Bot Created on: 10/Nov/23 17:04 Start Date: 10/Nov/23 17:04 Worklog Time Spent: 10m Work Description: jbonofre opened a new pull request, #1115: URL: https://github.com/apache/activemq/pull/1115 (no comment) Issue Time Tracking --- Worklog Id: (was: 889976) Remaining Estimate: 0h Time Spent: 10m > No authentication to access webconsole > -- > > Key: AMQ-9384 > URL: https://issues.apache.org/jira/browse/AMQ-9384 > Project: ActiveMQ > Issue Type: Bug > Components: Web Console >Affects Versions: 6.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > It seems that there's no authentication to access ActiveMQ admin/web console. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (AMQ-9328) Update website cleaning/mentioning ActiveMQ 6.0.0 and update activemq component
[ https://issues.apache.org/jira/browse/AMQ-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-9328 started by Matt Pavlovich. --- > Update website cleaning/mentioning ActiveMQ 6.0.0 and update activemq > component > --- > > Key: AMQ-9328 > URL: https://issues.apache.org/jira/browse/AMQ-9328 > Project: ActiveMQ > Issue Type: Improvement > Components: Documentation, website >Reporter: Jean-Baptiste Onofré >Assignee: Matt Pavlovich >Priority: Major > Fix For: 6.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9348) activemq-http MQTTWSConnectionTimeoutTest is failing
[
https://issues.apache.org/jira/browse/AMQ-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated AMQ-9348:
Fix Version/s: 6.1.0
(was: 6.0.0)
> activemq-http MQTTWSConnectionTimeoutTest is failing
>
>
> Key: AMQ-9348
> URL: https://issues.apache.org/jira/browse/AMQ-9348
> Project: ActiveMQ
> Issue Type: Bug
> Components: Test Cases
>Affects Versions: 6.0.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.1.0
>
>
> {{MQTTWSConnectionTimeoutTest}} (in {{activemq-http}} module) is failing:
> {code:java}
> [INFO] Running org.apache.activemq.transport.ws.MQTTWSConnectionTimeoutTest
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 61.09
> s <<< FAILURE! -- in
> org.apache.activemq.transport.ws.MQTTWSConnectionTimeoutTest
> [ERROR]
> org.apache.activemq.transport.ws.MQTTWSConnectionTimeoutTest.testInactivityMonitor
> -- Time elapsed: 61.05 s <<< FAILURE!
> java.lang.AssertionError: no dangling connections
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at
> org.apache.activemq.transport.ws.MQTTWSConnectionTimeoutTest.testInactivityMonitor(MQTTWSConnectionTimeoutTest.java:72)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.lang.Thread.run(Thread.java:840) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9348) activemq-http MQTTWSConnectionTimeoutTest is failing
[
https://issues.apache.org/jira/browse/AMQ-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785009#comment-17785009
]
Matt Pavlovich commented on AMQ-9348:
-
Moving this to v6.1.0 as it appears to be race / timing condition in the test,
and not a bug
> activemq-http MQTTWSConnectionTimeoutTest is failing
>
>
> Key: AMQ-9348
> URL: https://issues.apache.org/jira/browse/AMQ-9348
> Project: ActiveMQ
> Issue Type: Bug
> Components: Test Cases
>Affects Versions: 6.0.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.1.0
>
>
> {{MQTTWSConnectionTimeoutTest}} (in {{activemq-http}} module) is failing:
> {code:java}
> [INFO] Running org.apache.activemq.transport.ws.MQTTWSConnectionTimeoutTest
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 61.09
> s <<< FAILURE! -- in
> org.apache.activemq.transport.ws.MQTTWSConnectionTimeoutTest
> [ERROR]
> org.apache.activemq.transport.ws.MQTTWSConnectionTimeoutTest.testInactivityMonitor
> -- Time elapsed: 61.05 s <<< FAILURE!
> java.lang.AssertionError: no dangling connections
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at
> org.apache.activemq.transport.ws.MQTTWSConnectionTimeoutTest.testInactivityMonitor(MQTTWSConnectionTimeoutTest.java:72)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.lang.Thread.run(Thread.java:840) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4496) Allow auto-delete to be updated on a live queue
Stephen Baker created ARTEMIS-4496: -- Summary: Allow auto-delete to be updated on a live queue Key: ARTEMIS-4496 URL: https://issues.apache.org/jira/browse/ARTEMIS-4496 Project: ActiveMQ Artemis Issue Type: New Feature Components: Broker Affects Versions: 2.31.2 Reporter: Stephen Baker Request: Ability to set auto-delete to false on a live queue with the updateQueue operation. Motivation: Our expected process is to update the address list in broker.xml and touch the file before deploying any app that uses a new queue. We have auto-create-address and auto-create-queue enabled as per the default configuration. Sometimes, process is missed and an update is deployed which uses a new queue before it is defined in configuration. We have some of those addresses now in production because the process involves updating the applications again to shift to a new queue. Stopping the world to delete the queue and touch broker.xml is not an option, so our strategy to date has been to create a new queue and updating the application to migrate to it. This is much more time consuming than if we could reconfigure the queue/address through management. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9381) Upgrade to maven-surefire-plugin 3.2.1
[ https://issues.apache.org/jira/browse/AMQ-9381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9381: -- Fix Version/s: (was: 5.17.7) > Upgrade to maven-surefire-plugin 3.2.1 > -- > > Key: AMQ-9381 > URL: https://issues.apache.org/jira/browse/AMQ-9381 > Project: ActiveMQ > Issue Type: Dependency upgrade >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0, 5.18.4 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (AMQ-9381) Upgrade to maven-surefire-plugin 3.2.1
[ https://issues.apache.org/jira/browse/AMQ-9381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-9381. --- Resolution: Fixed > Upgrade to maven-surefire-plugin 3.2.1 > -- > > Key: AMQ-9381 > URL: https://issues.apache.org/jira/browse/AMQ-9381 > Project: ActiveMQ > Issue Type: Dependency upgrade >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0, 5.18.4 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9381) Upgrade to maven-surefire-plugin 3.2.1
[ https://issues.apache.org/jira/browse/AMQ-9381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784975#comment-17784975 ] ASF subversion and git services commented on AMQ-9381: -- Commit b79c6fffe036f4919ef55417b6e2e749d235a3e4 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=b79c6fffe ] AMQ-9381: Upgrade to maven-surefire-plugin 3.2.1 > Upgrade to maven-surefire-plugin 3.2.1 > -- > > Key: AMQ-9381 > URL: https://issues.apache.org/jira/browse/AMQ-9381 > Project: ActiveMQ > Issue Type: Dependency upgrade >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0, 5.18.4, 5.17.7 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9381) Upgrade to maven-surefire-plugin 3.2.1
[ https://issues.apache.org/jira/browse/AMQ-9381?focusedWorklogId=889954=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-889954 ] ASF GitHub Bot logged work on AMQ-9381: --- Author: ASF GitHub Bot Created on: 10/Nov/23 14:44 Start Date: 10/Nov/23 14:44 Worklog Time Spent: 10m Work Description: jbonofre merged PR #: URL: https://github.com/apache/activemq/pull/ Issue Time Tracking --- Worklog Id: (was: 889954) Time Spent: 20m (was: 10m) > Upgrade to maven-surefire-plugin 3.2.1 > -- > > Key: AMQ-9381 > URL: https://issues.apache.org/jira/browse/AMQ-9381 > Project: ActiveMQ > Issue Type: Dependency upgrade >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0, 5.18.4, 5.17.7 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9381) Upgrade to maven-surefire-plugin 3.2.1
[ https://issues.apache.org/jira/browse/AMQ-9381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784977#comment-17784977 ] ASF subversion and git services commented on AMQ-9381: -- Commit e78505dbfff3c0ce96fb046e860a8735b8f7bed4 in activemq's branch refs/heads/activemq-5.18.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=e78505dbf ] AMQ-9381: Upgrade to maven-surefire-plugin 3.2.1 (cherry picked from commit b79c6fffe036f4919ef55417b6e2e749d235a3e4) > Upgrade to maven-surefire-plugin 3.2.1 > -- > > Key: AMQ-9381 > URL: https://issues.apache.org/jira/browse/AMQ-9381 > Project: ActiveMQ > Issue Type: Dependency upgrade >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0, 5.18.4, 5.17.7 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9381) Upgrade to maven-surefire-plugin 3.2.1
[ https://issues.apache.org/jira/browse/AMQ-9381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784976#comment-17784976 ] ASF subversion and git services commented on AMQ-9381: -- Commit fb379997c6fc1201c2cf71b3d1f1dfb3c3a1bd3b in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=fb379997c ] Merge pull request # from jbonofre/AMQ-9381 AMQ-9381: Upgrade to maven-surefire-plugin 3.2.1 > Upgrade to maven-surefire-plugin 3.2.1 > -- > > Key: AMQ-9381 > URL: https://issues.apache.org/jira/browse/AMQ-9381 > Project: ActiveMQ > Issue Type: Dependency upgrade >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0, 5.18.4, 5.17.7 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9296) Add authentications support in ActiveMQ docker images
[ https://issues.apache.org/jira/browse/AMQ-9296?focusedWorklogId=889947=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-889947 ] ASF GitHub Bot logged work on AMQ-9296: --- Author: ASF GitHub Bot Created on: 10/Nov/23 14:14 Start Date: 10/Nov/23 14:14 Worklog Time Spent: 10m Work Description: jbonofre commented on PR #1050: URL: https://github.com/apache/activemq/pull/1050#issuecomment-1805817021 Superseded by #1114 1114 Issue Time Tracking --- Worklog Id: (was: 889947) Time Spent: 50m (was: 40m) > Add authentications support in ActiveMQ docker images > - > > Key: AMQ-9296 > URL: https://issues.apache.org/jira/browse/AMQ-9296 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Eddú Meléndez >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Docker images for Apache ActiveMQ have been published > [https://hub.docker.com/r/apache/activemq-classic/tags] > It would be great to support env vars for USER and PASSWORD to set the broker > credentials and be able to do `ActiveMQConnectionFactory(String userName, > String password, String brokerURL);` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9296) Add authentications support in ActiveMQ docker images
[ https://issues.apache.org/jira/browse/AMQ-9296?focusedWorklogId=889946=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-889946 ] ASF GitHub Bot logged work on AMQ-9296: --- Author: ASF GitHub Bot Created on: 10/Nov/23 14:14 Start Date: 10/Nov/23 14:14 Worklog Time Spent: 10m Work Description: jbonofre closed pull request #1050: [AMQ-9296] Add support of credentials to the docker image URL: https://github.com/apache/activemq/pull/1050 Issue Time Tracking --- Worklog Id: (was: 889946) Time Spent: 40m (was: 0.5h) > Add authentications support in ActiveMQ docker images > - > > Key: AMQ-9296 > URL: https://issues.apache.org/jira/browse/AMQ-9296 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Eddú Meléndez >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Docker images for Apache ActiveMQ have been published > [https://hub.docker.com/r/apache/activemq-classic/tags] > It would be great to support env vars for USER and PASSWORD to set the broker > credentials and be able to do `ActiveMQConnectionFactory(String userName, > String password, String brokerURL);` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9296) Add authentications support in ActiveMQ docker images
[ https://issues.apache.org/jira/browse/AMQ-9296?focusedWorklogId=889945=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-889945 ] ASF GitHub Bot logged work on AMQ-9296: --- Author: ASF GitHub Bot Created on: 10/Nov/23 14:13 Start Date: 10/Nov/23 14:13 Worklog Time Spent: 10m Work Description: jbonofre opened a new pull request, #1114: URL: https://github.com/apache/activemq/pull/1114 (no comment) Issue Time Tracking --- Worklog Id: (was: 889945) Time Spent: 0.5h (was: 20m) > Add authentications support in ActiveMQ docker images > - > > Key: AMQ-9296 > URL: https://issues.apache.org/jira/browse/AMQ-9296 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Eddú Meléndez >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Docker images for Apache ActiveMQ have been published > [https://hub.docker.com/r/apache/activemq-classic/tags] > It would be great to support env vars for USER and PASSWORD to set the broker > credentials and be able to do `ActiveMQConnectionFactory(String userName, > String password, String brokerURL);` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4476) Connection Failure Race Conditions in AMQP and Core
[ https://issues.apache.org/jira/browse/ARTEMIS-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784952#comment-17784952 ] ASF subversion and git services commented on ARTEMIS-4476: -- Commit 4838cb7725b887c0880427285501e4db5311d9fc in activemq-artemis's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=4838cb7725 ] ARTEMIS-4476: remove added duplicate dependency, fix build warning > Connection Failure Race Conditions in AMQP and Core > --- > > Key: ARTEMIS-4476 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4476 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Time Spent: 4h > Remaining Estimate: 0h > > Failure Detection has a possibility to a race condition with the processing > of the client packets (or frames in the case of AMQP). > This is because Netty detects the failure and removes the connection objects > while the packets are still processing things. > I was not able to reproduce this particular issue, but I have seen a case > from a memory dump where the consumer was created while the connection was > already dropped, leaving the consumer isolated without any communication with > clients. > That particular case I could see a possibility because of these races. > I am adding tests to exercise connection failure in stress and I was able to > reproduce other issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9383) Websocket transport options do not get applied
[
https://issues.apache.org/jira/browse/AMQ-9383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784934#comment-17784934
]
Christopher L. Shannon commented on AMQ-9383:
-
[~jbonofre] - That makes sense, thanks for the clarification
> Websocket transport options do not get applied
> --
>
> Key: AMQ-9383
> URL: https://issues.apache.org/jira/browse/AMQ-9383
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
>Affects Versions: 5.15.16, 5.18.3, 5.17.6, 5.16.7
>Reporter: Kostiantyn Miklevskyi
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.0.0, 5.18.4, 5.17.7, 5.16.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Configure broker transport connector like this:
> {code:java}
> uri="ws://0.0.0.0:5680?amqp.traceFrames=truewireFormat=amqpwireFormat.transformer=jmswireFormat.allowNonSaslConnections=true"/>
> {code}
>
> Try to connect to this instance with rhea.js library.
> First attempt to connect would be successful.
> Second and all subsequent attempts would fail.
> The only way to "fix" this would be a broker restart.
>
> The issue is here:
> [https://github.com/apache/activemq/blob/4bbb055187166706103d785e9665efb439792c51/activemq-http/src/main/java/org/apache/activemq/transport/ws/jetty9/WSServlet.java#L162]
>
> transportOptions would be "consumed" by introspection on the first connection
> attempt, and on subsequent attempts "allowNonSaslConnections" and
> "transformer" would not be there, so won't be applied to wireformat and the
> result would be an error.
>
> Interestingly this was already spotted and fixed in the same class for MQTT
> subprotocol here:
> [https://github.com/apache/activemq/blob/4bbb055187166706103d785e9665efb439792c51/activemq-http/src/main/java/org/apache/activemq/transport/ws/jetty9/WSServlet.java#L115C86-L115C86]
> by simply creating a copy of transport options before sending it into
> introspecting setters.
>
> Please apply the same fix.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9383) Websocket transport options do not get applied
[
https://issues.apache.org/jira/browse/AMQ-9383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784931#comment-17784931
]
Jean-Baptiste Onofré commented on AMQ-9383:
---
[~cshannon] I merged on activemq-5.16.x just in case but I don't plan 5.16.x
new release. I will do 5.17/5.18/6.0.
> Websocket transport options do not get applied
> --
>
> Key: AMQ-9383
> URL: https://issues.apache.org/jira/browse/AMQ-9383
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
>Affects Versions: 5.15.16, 5.18.3, 5.17.6, 5.16.7
>Reporter: Kostiantyn Miklevskyi
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.0.0, 5.18.4, 5.17.7, 5.16.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Configure broker transport connector like this:
> {code:java}
> uri="ws://0.0.0.0:5680?amqp.traceFrames=truewireFormat=amqpwireFormat.transformer=jmswireFormat.allowNonSaslConnections=true"/>
> {code}
>
> Try to connect to this instance with rhea.js library.
> First attempt to connect would be successful.
> Second and all subsequent attempts would fail.
> The only way to "fix" this would be a broker restart.
>
> The issue is here:
> [https://github.com/apache/activemq/blob/4bbb055187166706103d785e9665efb439792c51/activemq-http/src/main/java/org/apache/activemq/transport/ws/jetty9/WSServlet.java#L162]
>
> transportOptions would be "consumed" by introspection on the first connection
> attempt, and on subsequent attempts "allowNonSaslConnections" and
> "transformer" would not be there, so won't be applied to wireformat and the
> result would be an error.
>
> Interestingly this was already spotted and fixed in the same class for MQTT
> subprotocol here:
> [https://github.com/apache/activemq/blob/4bbb055187166706103d785e9665efb439792c51/activemq-http/src/main/java/org/apache/activemq/transport/ws/jetty9/WSServlet.java#L115C86-L115C86]
> by simply creating a copy of transport options before sending it into
> introspecting setters.
>
> Please apply the same fix.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
