[jira] [Resolved] (ARTEMIS-4771) NPE between AMQPLargeMessageWriter::tryDelivering and resetClose
[ https://issues.apache.org/jira/browse/ARTEMIS-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4771. - Fix Version/s: 2.34.0 Resolution: Fixed > NPE between AMQPLargeMessageWriter::tryDelivering and resetClose > > > Key: ARTEMIS-4771 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4771 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.34.0 > > Time Spent: 3h 20m > Remaining Estimate: 0h > > This is using RedHat's bits: > java.lang.NullPointerException: Cannot invoke > "org.apache.qpid.proton.engine.Delivery.getTag()" because "this.delivery" is > null > at > org.apache.activemq.artemis.protocol.amqp.proton.AMQPLargeMessageWriter.tryDelivering(AMQPLargeMessageWriter.java:174) > ~[artemis-amqp-protocol-2.33.0.redhat-9.jar:2.33.0.redhat-9] > at > io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173) > ~[netty-common-4.1.108.Final-redhat-1.jar:4.1.108.Final-redhat-1] > at > io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166) > [netty-common-4.1.108.Final-redhat-1.jar:4.1.108.Final-redhat-1] > at > io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) > [netty-common-4.1.108.Final-redhat-1.jar:4.1.108.Final-redhat-1] > at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:413) > [netty-transport-classes-epoll-4.1.108.Final-redhat-1.jar:4.1.108.Final-redhat-1] > at > io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) > [netty-common-4.1.108.Final-redhat-1.jar:4.1.108.Final-redhat-1] > at > io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) > [netty-common-4.1.108.Final-redhat-1.jar:4.1.108.Final-redhat-1] > at > org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118) > [artemis-commons-2.33.0.redhat-9.jar:2.33.0.redhat-9] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4778) misc test cleanup
[ https://issues.apache.org/jira/browse/ARTEMIS-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4778. - Resolution: Fixed > misc test cleanup > - > > Key: ARTEMIS-4778 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4778 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Tests >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.34.0 > > > There are various tests oddites that could be cleaned up, such as: test > classes that have nested classes mixing both parameterized and > non-parameterized, or test classes that have hierarchies that result in > hundreds of duplicate runs of the same self-contained tests from a parent, or > skipping hundreds of tests by 'un-parameterizing' a parent, or tests that > influence static config without restoring it afterwards even in the case of > tests that are being skipped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4778) misc test cleanup
Robbie Gemmell created ARTEMIS-4778: --- Summary: misc test cleanup Key: ARTEMIS-4778 URL: https://issues.apache.org/jira/browse/ARTEMIS-4778 Project: ActiveMQ Artemis Issue Type: Task Components: Tests Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.34.0 There are various tests oddites that could be cleaned up, such as: test classes that have nested classes mixing both parameterized and non-parameterized, or test classes that have hierarchies that result in hundreds of duplicate runs of the same self-contained tests from a parent, or skipping hundreds of tests by 'un-parameterizing' a parent, or tests that influence static config without restoring it afterwards even in the case of tests that are being skipped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-3622) MQTT can deadlock on client connection / disconnection
[
https://issues.apache.org/jira/browse/ARTEMIS-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-3622.
-
Fix Version/s: 2.34.0
Resolution: Fixed
> MQTT can deadlock on client connection / disconnection
> --
>
> Key: ARTEMIS-3622
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3622
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.19.0
> Environment: Using the latest java 17 and artemis 2.19 but looking at
> the code, it should affect 2.20 as well.
>Reporter: Marcelo Takeshi Fukushima
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.34.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> It seems that the {{MQTTProtocolHandler}} and {{MQTTConnectionManager}} are
> on a racing condition and can deadlock themselves on misbehaving clients. I'm
> including the relevant stack trace (ignore thread 11 that is just waiting for
> the lock).
> Looking at the relevant code, it seems that the clean-up thread (88 on the
> {{{}MQTTFailureListener{}}}) starts cleaning up the session state and then
> the session, but when {{MQTTSession.stop}} calls
> {{{}MQTTSessionState.clear{}}}, the session state is no longer the same (a
> racy connection has replaced the session state with a brand new under the
> same client-id).
> I think the methods connect and disconnect on the {{MQTTConnectionManager}}
> could be marked as synchronized as a whole, to prevent racy connects /
> disconnects (but since I don't know all the ins and outs of the code, you
> guys might have a better fix).
> {noformat}
> Found one Java-level deadlock:
> =
> "Thread-11
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@640f11a1)":
> waiting to lock monitor 0x7f6d003368c0 (object 0x00045f29f240, a
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTSessionState),
> which is held by "Thread-24
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@640f11a1)"
> "Thread-24
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@640f11a1)":
> waiting to lock monitor 0x7f6d00336a80 (object 0x00045f2a1068, a
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTSession),
> which is held by "Thread-88
> (ActiveMQ-remoting-threads-ActiveMQServerImpl::name=0.0.0.0-212232499)"
> "Thread-88
> (ActiveMQ-remoting-threads-ActiveMQServerImpl::name=0.0.0.0-212232499)":
> waiting to lock monitor 0x7f6d003368c0 (object 0x00045f29f240, a
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTSessionState),
> which is held by "Thread-24
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@640f11a1)"
> Java stack information for the threads listed above:
> ===
> "Thread-11
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@640f11a1)":
> at
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTConnectionManager.disconnect(MQTTConnectionManager.java:150)
> - waiting to lock <0x00045f29f240> (a
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTSessionState)
> at
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTFailureListener.connectionFailed(MQTTFailureListener.java:37)
> at
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTConnection.fail(MQTTConnection.java:150)
> at
> org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$FailureCheckAndFlushThread$2.run(RemotingServiceImpl.java:780)
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:65)
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase$$Lambda$137/0x000800e01dc8.run(Unknown
> Source)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.1/ThreadPoolExecutor.java:1136)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@17.0.1/ThreadPoolExecutor.java:635)
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> "Thread-24
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@640f11a1)":
> at
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTSession.start(MQTTSession.java:87)
> - waiting to lock <0x00045f2a1068> (a
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTSession)
> at
>
[jira] [Resolved] (ARTEMIS-4769) Update to pem-keystore 2.4.0
[ https://issues.apache.org/jira/browse/ARTEMIS-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4769. - Resolution: Fixed > Update to pem-keystore 2.4.0 > > > Key: ARTEMIS-4769 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4769 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.34.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4770) Update to bouncycastle 1.78
[ https://issues.apache.org/jira/browse/ARTEMIS-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4770. - Resolution: Fixed > Update to bouncycastle 1.78 > --- > > Key: ARTEMIS-4770 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4770 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.34.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4770) Update to bouncycastle 1.78
Robbie Gemmell created ARTEMIS-4770: --- Summary: Update to bouncycastle 1.78 Key: ARTEMIS-4770 URL: https://issues.apache.org/jira/browse/ARTEMIS-4770 Project: ActiveMQ Artemis Issue Type: Dependency upgrade Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.34.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4769) Update to pem-keystore 2.4.0
Robbie Gemmell created ARTEMIS-4769: --- Summary: Update to pem-keystore 2.4.0 Key: ARTEMIS-4769 URL: https://issues.apache.org/jira/browse/ARTEMIS-4769 Project: ActiveMQ Artemis Issue Type: Dependency upgrade Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.34.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4752) Upgrade ErrorProne to 2.27.0
[ https://issues.apache.org/jira/browse/ARTEMIS-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4752. - Fix Version/s: 2.34.0 Resolution: Fixed > Upgrade ErrorProne to 2.27.0 > > > Key: ARTEMIS-4752 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4752 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.34.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4754) Make configuring security for AMQP federation user accounts simpler
[ https://issues.apache.org/jira/browse/ARTEMIS-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4754. - Resolution: Fixed > Make configuring security for AMQP federation user accounts simpler > --- > > Key: ARTEMIS-4754 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4754 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: AMQP >Affects Versions: 2.33.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.34.0 > > Time Spent: 40m > Remaining Estimate: 0h > > When creating the user account used to restrict access when securing an AMQP > federation account the currently implementation requires giving the > federation overly broad access so that it can create control and event queues > used for its internal mechanisms. We should make this easier and more narrow > so that a federation user can be granted access to a more limited set of > resources for internal federation mechanics besides access to those addresses > and queues which will be targets of federation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4680) Upgrade the console to use HawtIO 4
[ https://issues.apache.org/jira/browse/ARTEMIS-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4680. - Resolution: Fixed > Upgrade the console to use HawtIO 4 > --- > > Key: ARTEMIS-4680 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4680 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: console-1.0.0 > > Time Spent: 9.5h > Remaining Estimate: 0h > > The current console is based upon HawtIO 1 which in turn is built on > Bootstrap. Bootstrap is old and no longer actively being maintained. > > This improvement is to migrate the current console to use HawtIO 4 which i > based on Typescript, react and Patternfly. > > As it can run standalone and be built seperately, this will be released > independently from [https://github.com/apache/activemq-artemis-console] and > the output later consumed in Artemis releases (similar to artemis-native). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4680) Upgrade the console to use HawtIO 4
[ https://issues.apache.org/jira/browse/ARTEMIS-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4680: Description: The current console is based upon HawtIO 1 which in turn is built on Bootstrap. Bootstrap is old and no longer actively being maintained. This improvement is to migrate the current console to use HawtIO 4 which i based on Typescript, react and Patternfly. As it can run standalone and be built seperately, this will be released independently from [https://github.com/apache/activemq-artemis-console] and the output later consumed in Artemis releases (similar to artemis-native). was: The current console is based upon HawtIO 1 which in turn is built on Bootstrap. Bootstrap is old and no longer actively being maintained. This improvement is to migrate the current console to use HawtIO 4 which i based on Typescript, react and Patternfly. As it can run standalone and be built seperately, this will be released independently from [https://github.com/apache/activemq-artemis-console/pull/2] and the output later consumed in Artemis releases (similar to artemis-native). > Upgrade the console to use HawtIO 4 > --- > > Key: ARTEMIS-4680 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4680 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: console-1.0.0 > > Time Spent: 9.5h > Remaining Estimate: 0h > > The current console is based upon HawtIO 1 which in turn is built on > Bootstrap. Bootstrap is old and no longer actively being maintained. > > This improvement is to migrate the current console to use HawtIO 4 which i > based on Typescript, react and Patternfly. > > As it can run standalone and be built seperately, this will be released > independently from [https://github.com/apache/activemq-artemis-console] and > the output later consumed in Artemis releases (similar to artemis-native). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4680) Upgrade the console to use HawtIO 4
[ https://issues.apache.org/jira/browse/ARTEMIS-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4680: Description: The current console is based upon HawtIO 1 which in turn is built on Bootstrap. Bootstrap is old and no longer actively being maintained. This improvement is to migrate the current console to use HawtIO 4 which i based on Typescript, react and Patternfly. As it can run standalone and be built seperately, this will be released independently from [https://github.com/apache/activemq-artemis-console/pull/2] and the output later consumed in Artemis releases (similar to artemis-native). was: The current console is based upon HawtIO 1 which in turn is built on Bootstrap. Bootstrap is old and no longer actively being maintained. This improvement is to migrate the current console to use HawtIO 4 which i based on Typescript, react and Patternfly. > Upgrade the console to use HawtIO 4 > --- > > Key: ARTEMIS-4680 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4680 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: console-1.0.0 > > Time Spent: 9.5h > Remaining Estimate: 0h > > The current console is based upon HawtIO 1 which in turn is built on > Bootstrap. Bootstrap is old and no longer actively being maintained. > > This improvement is to migrate the current console to use HawtIO 4 which i > based on Typescript, react and Patternfly. > > As it can run standalone and be built seperately, this will be released > independently from > [https://github.com/apache/activemq-artemis-console/pull/2] and the output > later consumed in Artemis releases (similar to artemis-native). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4680) Upgrade the console to use HawtIO 4
[ https://issues.apache.org/jira/browse/ARTEMIS-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4680: Description: The current console is based upon HawtIO 1 which in turn is built on Bootstrap. Bootstrap is old and no longer actively being maintained. This improvement is to migrate the current console to use HawtIO 4 which i based on Typescript, react and Patternfly. was: The current console is based upon HawtIO 1 which in turn is built on Bootstrap. Bootstrap is old and no longer actively being maintained. This improvement is to migrate the current console to use HawtIO 4 which i based on Typescript, react and Patternfly. A WIP can be found [here|https://github.com/andytaylor/activemq-artemis/tree/artemis-console-ng] > Upgrade the console to use HawtIO 4 > --- > > Key: ARTEMIS-4680 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4680 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: console-1.0.0 > > Time Spent: 9.5h > Remaining Estimate: 0h > > The current console is based upon HawtIO 1 which in turn is built on > Bootstrap. Bootstrap is old and no longer actively being maintained. > > This improvement is to migrate the current console to use HawtIO 4 which i > based on Typescript, react and Patternfly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4680) Upgrade the console to use HawtIO 4
[ https://issues.apache.org/jira/browse/ARTEMIS-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4680: Fix Version/s: console-1.0.0 > Upgrade the console to use HawtIO 4 > --- > > Key: ARTEMIS-4680 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4680 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: console-1.0.0 > > Time Spent: 9.5h > Remaining Estimate: 0h > > The current console is based upon HawtIO 1 which in turn is built on > Bootstrap. Bootstrap is old and no longer actively being maintained. > > This improvement is to migrate the current console to use HawtIO 4 which i > based on Typescript, react and Patternfly. > > A WIP can be found > [here|https://github.com/andytaylor/activemq-artemis/tree/artemis-console-ng] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4745) Allow configuration of AMQP federation pull consumer batch size
[ https://issues.apache.org/jira/browse/ARTEMIS-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4745. - Resolution: Fixed > Allow configuration of AMQP federation pull consumer batch size > > > Key: ARTEMIS-4745 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4745 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: AMQP >Affects Versions: 2.33.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: 2.34.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When Queue federation receiver links are configured to only pull messages > from the remote when local capacity allows it they grant a fixed credit > window amount of link credits currently. In some cases control over this > batch size value is beneficial. We can add an additional configuration > property to convey this limit to the federation configuration -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4744) AMQP broker connections don't fully support multi host URIs
[ https://issues.apache.org/jira/browse/ARTEMIS-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4744. - Resolution: Fixed > AMQP broker connections don't fully support multi host URIs > --- > > Key: ARTEMIS-4744 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4744 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.33.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.34.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > When configuring a multi host connection URI for an AMQP broker connection > the connection will utilize some but not all of the configuration. The > broker will attempt connection to each host and port part specific on the URI > but does not apply configuration specific to a given host. This can lead to > failure on connect due to using the TLS configuration from the first host > when attempting to connect to the following N hosts. Users need to be able > to configure TLS specific options per host as values such as host > verification, SNI and trust stores can vary amongst hosts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4737) DOESNT OVERRIDE EQUALS in ConnectionFactoryProperties.java
[ https://issues.apache.org/jira/browse/ARTEMIS-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed ARTEMIS-4737. --- Resolution: Duplicate > DOESNT OVERRIDE EQUALS in ConnectionFactoryProperties.java > -- > > Key: ARTEMIS-4737 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4737 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Galkin Alexey >Priority: Major > > The class overrides the equals method, but does not implement its logic. > Instead, it compares objects by their classes using the getClass() method ( > if (getClass() != obj.getClass()) [line > 748|https://github.com/apache/activemq-artemis/blob/main/artemis-ra/src/main/java/org/apache/activemq/artemis/ra/ConnectionFactoryProperties.java]), > which can lead to incorrect object comparisons. For the equals method to > work correctly, you need to override its logic so that it compares objects by > their fields or other criteria, and not just by their classes. > > Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE. > Author Alexey Galkin. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-1921) Setting client ID on core JMS should be reflected in broker RemotingConnection
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-1921. - Fix Version/s: 2.34.0 Resolution: Fixed > Setting client ID on core JMS should be reflected in broker RemotingConnection > -- > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Assignee: Justin Bertram >Priority: Major > Fix For: 2.34.0 > > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > Time Spent: 20m > Remaining Estimate: 0h > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1921) Setting client ID on core JMS should be reflected in broker RemotingConnection
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838597#comment-17838597 ] Robbie Gemmell commented on ARTEMIS-1921: - Yep, wasn't commenting on the change (hadn't looked yet) but just the earlier reply around why it didnt work (but doing one or the other probably did previously due to other oddness). Have looked at the new change now and looks good. > Setting client ID on core JMS should be reflected in broker RemotingConnection > -- > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Assignee: Justin Bertram >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > Time Spent: 10m > Remaining Estimate: 0h > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4625) Upgrade CheckStyle to 10.15.0
[ https://issues.apache.org/jira/browse/ARTEMIS-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4625. - Fix Version/s: 2.34.0 Resolution: Fixed > Upgrade CheckStyle to 10.15.0 > - > > Key: ARTEMIS-4625 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4625 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.34.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1921) Setting client ID on core JMS should be reflected in broker RemotingConnection
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837645#comment-17837645 ] Robbie Gemmell commented on ARTEMIS-1921: - Not sure we should be expecting a response after 6 years, but it seems possible the code was a minimal attempt to show 'it isnt available on Core at all' rather than simply 'it is available at this point on the others', perhaps the use case is something else later where it is available on the others. Or maybe some behaviour changed in those 6 years and it used to be available; I actually think it might have in the AMQP case, I seem to recall it doing something odd like calling the auth methods when the first session opened like Core. Not sure it does that anymore. The ClientID wont be available at the point Qpid JMS actually goes through the SASL process, since it hasnt been sent yet, regardless how the client is configured, auth happens 'before connection' rather than during. If the broker fails the SASL negotiation, the client wont even get as far as starting a bare AMQP connection which is where the ClientId is carried as the container-id. I presume it is failing auth in this case and throwing. If it doenst fail auth, the test/application code will still throw with Qpid JMS since it is _both_ setting the ClientID up front 'administratively', and then also trying to set it after Connection creation, whereas you can only do one or the other. The second will throw an ISE if it gets that far. > Setting client ID on core JMS should be reflected in broker RemotingConnection > -- > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > Time Spent: 10m > Remaining Estimate: 0h > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1921) Setting clientID in artemis-jms-client has no effect
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837387#comment-17837387 ] Robbie Gemmell commented on ARTEMIS-1921: - I wasn't really getting into whether the current implementation is actually able to do what was expected, just noting the attached application code did also do something that is portable, which your reply didnt seem to cover by concentrating only on the other bit that isnt. Reading again, it also seems like you were suggesting it only works for Qpid JMS due to setting it on the ConnectionFactory, but I dont believe that is the case. If a ClientID wasnt set on the ConnectionFactory 'administratively' (i.e via impl-detail setter or its URI options) then the client will actually create the TCP connection and authenticate, but defer establishing the bare AMQP connection (which carries the ClientID as its container-id) until such time a Connection method is called, like setClientID first if you want to set the ClientID (and it hasnt been set 'administratively' already), or any other method if you don't want to (and havent already) set it . The client can be configured not to defer the bare AMQP connection like this, if you know you wont set a clientID and also e.g want to take a while before using the Connection. > Setting clientID in artemis-jms-client has no effect > > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-1921) Setting clientID in artemis-jms-client has no effect
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837376#comment-17837376 ] Robbie Gemmell edited comment on ARTEMIS-1921 at 4/15/24 5:19 PM: -- The attached code tries _both_ the ConnectionFactory method that is impl-detail and not part of the API (though is in the vein of 'administratively configured' values the spec does speak to), as well as the Connection method that _is_ part of the spec. The latter is portable. was (Author: gemmellr): The attached code tries _both_ the ConnectionFactory method that is impl-detail and not part of the APUI (though is in the vein of 'administratively configured' values the spec does speak to), as well as the Connection method that _is_ part of the spec. The latter is portable. > Setting clientID in artemis-jms-client has no effect > > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1921) Setting clientID in artemis-jms-client has no effect
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837376#comment-17837376 ] Robbie Gemmell commented on ARTEMIS-1921: - The attached code tries _both_ the ConnectionFactory method that is impl-detail and not part of the APUI (though is in the vein of 'administratively configured' values the spec does speak to), as well as the Connection method that _is_ part of the spec. The latter is portable. > Setting clientID in artemis-jms-client has no effect > > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4528) TLS support PEM format for key and trust store type
[ https://issues.apache.org/jira/browse/ARTEMIS-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837207#comment-17837207 ] Robbie Gemmell commented on ARTEMIS-4528: - (Though only in the sense that its possible to operate without it, so you could now _exclude_ it, but its still there otherwise...i.e pem-keystore still isnt listed as an optional dependency in the maven sense). > TLS support PEM format for key and trust store type > --- > > Key: ARTEMIS-4528 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4528 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.31.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.32.0 > > Time Spent: 4.5h > Remaining Estimate: 0h > > managing key and trust store passwords when the credentials are securely > stored or managed by other means is a nuisance. > there is a nice PEM keystore provider at: > [https://github.com/ctron/pem-keystore] > This gives us an intuitive way to easily reference a simple cert or key > without a password as is the case with jsk or pkcs12 > name="netty-ssl-acceptor">tcp://localhost:5500?sslEnabled=true;keyStorePath=server-keystore.pem;keyStoreType=PEM > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4720) Add additional example for AMQP federation showing TLS configuration
[ https://issues.apache.org/jira/browse/ARTEMIS-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4720. - Resolution: Fixed > Add additional example for AMQP federation showing TLS configuration > > > Key: ARTEMIS-4720 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4720 > Project: ActiveMQ Artemis > Issue Type: Task > Components: ActiveMQ-Artemis-Examples, AMQP >Affects Versions: 2.33.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Trivial > Fix For: 2.34.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Add a new example in the AMQP Federation examples showing how to configure > the broker connections to use TLS to connect to the remote. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4710) Keep pem-keystore dependencies as is; make it really optional
[ https://issues.apache.org/jira/browse/ARTEMIS-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4710. - Fix Version/s: 2.34.0 Resolution: Fixed > Keep pem-keystore dependencies as is; make it really optional > - > > Key: ARTEMIS-4710 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4710 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.33.0 >Reporter: Alexey Markevich >Priority: Minor > Fix For: 2.34.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Previously we excluded bcprov-jdk15on and bcpkix-jdk15on dependencies > normally used by pem-keystore, and replaced them with bcprov-jdk18on and > bcpkix-jdk18on as already managed and used elsewhere in the build, thus > keeping things consistent on a single gav for the bc modules. > The latest 2.3.0 version of pem-keystore (used since ARTEMIS-4599) was > actually changed to use bcprov-jdk18on and bcpkix-jdk18on in > https://github.com/ctron/pem-keystore/commit/1263b207da0adf4a7d2dc61d6a9a19e7bba97731. > As such we can now simplify the dependency handling by removing the prior > exclusion+replacement handling for those deps. > Additionally, by avoiding a global import on PemKeyStoreProvider, and only > referencing it upon use, those who wish would be able to exclude the > dependency when the functionality is not used. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4710) Keep pem-keystore dependencies as is; make it really optional
[ https://issues.apache.org/jira/browse/ARTEMIS-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4710: Description: Previously we excluded bcprov-jdk15on and bcpkix-jdk15on dependencies normally used by pem-keystore, and replaced them with bcprov-jdk18on and bcpkix-jdk18on as already managed and used elsewhere in the build, thus keeping things consistent on a single gav for the bc modules. The latest 2.3.0 version of pem-keystore (used since ARTEMIS-4599) was actually changed to use bcprov-jdk18on and bcpkix-jdk18on in https://github.com/ctron/pem-keystore/commit/1263b207da0adf4a7d2dc61d6a9a19e7bba97731. As such we can now simplify the dependency handling by removing the prior exclusion+replacement handling for those deps. Additionally, by avoiding a global import on PemKeyStoreProvider, and only referencing it upon use, those who wish would be able to exclude the dependency when the functionality is not used. was: The latest version already uses bcprov-jdk18on. Avoid global imports to be able to exclude dependency when not used. > Keep pem-keystore dependencies as is; make it really optional > - > > Key: ARTEMIS-4710 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4710 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.33.0 >Reporter: Alexey Markevich >Priority: Minor > > Previously we excluded bcprov-jdk15on and bcpkix-jdk15on dependencies > normally used by pem-keystore, and replaced them with bcprov-jdk18on and > bcpkix-jdk18on as already managed and used elsewhere in the build, thus > keeping things consistent on a single gav for the bc modules. > The latest 2.3.0 version of pem-keystore (used since ARTEMIS-4599) was > actually changed to use bcprov-jdk18on and bcpkix-jdk18on in > https://github.com/ctron/pem-keystore/commit/1263b207da0adf4a7d2dc61d6a9a19e7bba97731. > As such we can now simplify the dependency handling by removing the prior > exclusion+replacement handling for those deps. > Additionally, by avoiding a global import on PemKeyStoreProvider, and only > referencing it upon use, those who wish would be able to exclude the > dependency when the functionality is not used. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4703) Add additional Queue federation example for AMQP federation
[ https://issues.apache.org/jira/browse/ARTEMIS-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4703. - Resolution: Fixed > Add additional Queue federation example for AMQP federation > --- > > Key: ARTEMIS-4703 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4703 > Project: ActiveMQ Artemis > Issue Type: Task > Components: AMQP >Affects Versions: 2.33.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Trivial > Fix For: 2.34.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Add an additional Queue federation example showing how to federate queue > messages through an intermediary broker that has no local-consumer demand, > just federation demand. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4703) Add additional Queue federation example for AMQP federation
[ https://issues.apache.org/jira/browse/ARTEMIS-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4703: Description: Add an additional Queue federation example showing how to federate queue messages through an intermediary broker that has no local-consumer demand, just federation demand. (was: Add an additional Queue federation example showing how to federate queue messages through an intermediary broker.) > Add additional Queue federation example for AMQP federation > --- > > Key: ARTEMIS-4703 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4703 > Project: ActiveMQ Artemis > Issue Type: Task > Components: AMQP >Affects Versions: 2.33.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Trivial > Fix For: 2.34.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Add an additional Queue federation example showing how to federate queue > messages through an intermediary broker that has no local-consumer demand, > just federation demand. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4701) Update to Netty 4.1.108
Robbie Gemmell created ARTEMIS-4701: --- Summary: Update to Netty 4.1.108 Key: ARTEMIS-4701 URL: https://issues.apache.org/jira/browse/ARTEMIS-4701 Project: ActiveMQ Artemis Issue Type: Dependency upgrade Reporter: Robbie Gemmell Fix For: 2.34.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4657) Support better correlation ID compatibility between JMS clients
[
https://issues.apache.org/jira/browse/ARTEMIS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated ARTEMIS-4657:
Summary: Support better correlation ID compatibility between JMS clients
(was: Support correlation ID compatibility between JMS clients)
> Support better correlation ID compatibility between JMS clients
> ---
>
> Key: ARTEMIS-4657
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4657
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.33.0
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Currently there are some use-cases with both {{String}} and {{byte[]}} values
> of JMS correlation ID that don't work between Core, OpenWire, and AMQP. We
> should support as many as possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4657) Support correlation ID compatibility between JMS clients
[
https://issues.apache.org/jira/browse/ARTEMIS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-4657.
-
Fix Version/s: 2.33.0
Resolution: Fixed
> Support correlation ID compatibility between JMS clients
>
>
> Key: ARTEMIS-4657
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4657
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.33.0
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Currently there are some use-cases with both {{String}} and {{byte[]}} values
> of JMS correlation ID that don't work between Core, OpenWire, and AMQP. We
> should support as many as possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4631) Upgrade Spring to 5.3.33
[ https://issues.apache.org/jira/browse/ARTEMIS-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4631: Summary: Upgrade Spring to 5.3.33 (was: Upgrade Spring to 5.3.32) > Upgrade Spring to 5.3.33 > > > Key: ARTEMIS-4631 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4631 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.33.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4683) Add additional examples for AMQP federation
[ https://issues.apache.org/jira/browse/ARTEMIS-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4683. - Resolution: Fixed > Add additional examples for AMQP federation > --- > > Key: ARTEMIS-4683 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4683 > Project: ActiveMQ Artemis > Issue Type: Task > Components: AMQP >Affects Versions: 2.32.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: 2.33.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Add additional examples to the features examples demonstrating various > configurations for AMQP federation so setup common typologies or use cases > such as multicast fanout or queue federation priority settings. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4648) Support typed properties on CLI producer
[ https://issues.apache.org/jira/browse/ARTEMIS-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4648. - Fix Version/s: 2.33.0 Resolution: Fixed > Support typed properties on CLI producer > > > Key: ARTEMIS-4648 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4648 > Project: ActiveMQ Artemis > Issue Type: New Feature >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.33.0 > > Time Spent: 3h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4672) Upgrade Netty to 4.107.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4672. - Fix Version/s: 2.33.0 Resolution: Fixed > Upgrade Netty to 4.107.Final > > > Key: ARTEMIS-4672 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4672 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Emmanuel Hugonnet >Priority: Major > Fix For: 2.33.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4655) Report logging metrics
[
https://issues.apache.org/jira/browse/ARTEMIS-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-4655.
-
Fix Version/s: 2.33.0
Resolution: Fixed
> Report logging metrics
> --
>
> Key: ARTEMIS-4655
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4655
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.33.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> External systems (e.g. Prometheus & Grafana) can consume metrics to visualize
> and monitor the health and performance of the broker. These systems often
> support configurable alerts to inform administrators of problems (e.g. long
> GC pauses, message accumulation, etc.). It may be useful to configure alerts
> for {{ERROR}} or {{WARN}} events in the log which may go unnoticed otherwise.
> The
> [Log4j2Metrics.java|https://github.com/micrometer-metrics/micrometer/blob/main/micrometer-core/src/main/java/io/micrometer/core/instrument/binder/logging/Log4j2Metrics.java]
> provided by Micrometer will report metrics for each logging category so
> administrators can see when unexpected events occur.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4621) Upgrade PostgreSQL to 42.7.2
[ https://issues.apache.org/jira/browse/ARTEMIS-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4621. - Resolution: Fixed > Upgrade PostgreSQL to 42.7.2 > > > Key: ARTEMIS-4621 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4621 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.33.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4631) Upgrade Spring to 5.3.32
[ https://issues.apache.org/jira/browse/ARTEMIS-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4631. - Resolution: Fixed > Upgrade Spring to 5.3.32 > > > Key: ARTEMIS-4631 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4631 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.33.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ARTEMIS-4631) Upgrade Spring to 5.3.31
[ https://issues.apache.org/jira/browse/ARTEMIS-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened ARTEMIS-4631: - > Upgrade Spring to 5.3.31 > > > Key: ARTEMIS-4631 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4631 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.33.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4621) Upgrade PostgreSQL to 42.7.2
[ https://issues.apache.org/jira/browse/ARTEMIS-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4621: Summary: Upgrade PostgreSQL to 42.7.2 (was: Upgrade PostgreSQL to 42.7.1) > Upgrade PostgreSQL to 42.7.2 > > > Key: ARTEMIS-4621 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4621 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.33.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4631) Upgrade Spring to 5.3.32
[ https://issues.apache.org/jira/browse/ARTEMIS-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4631: Summary: Upgrade Spring to 5.3.32 (was: Upgrade Spring to 5.3.31) > Upgrade Spring to 5.3.32 > > > Key: ARTEMIS-4631 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4631 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.33.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ARTEMIS-4621) Upgrade PostgreSQL to 42.7.1
[ https://issues.apache.org/jira/browse/ARTEMIS-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened ARTEMIS-4621: - > Upgrade PostgreSQL to 42.7.1 > > > Key: ARTEMIS-4621 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4621 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.33.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4658) AMQP Federation should prevent reflection of multicast messages between nodes
[ https://issues.apache.org/jira/browse/ARTEMIS-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4658. - Resolution: Fixed > AMQP Federation should prevent reflection of multicast messages between nodes > - > > Key: ARTEMIS-4658 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4658 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: AMQP >Affects Versions: 2.32.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.33.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When using a topology where brokers are dual federating messages for > addresses the federation producers and consumers should prevent reflection > between the two nodes. This allows for more complex configuration where the > max hops value is insufficient to prevent duplicates and cases of infinite > reflection if the user forgets to configure max hops. > Such a case would be a hub and spoke type setup where the producers and > consumers are on each of the spokes and the hub is the way point, here the > max hops needs to be set to '2' but this allows for a reflection from the hub > back to the sending spoke. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ARTEMIS-4656) Remove superfluous artemis-spring-integration module
[ https://issues.apache.org/jira/browse/ARTEMIS-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned ARTEMIS-4656: --- Assignee: Robbie Gemmell > Remove superfluous artemis-spring-integration module > > > Key: ARTEMIS-4656 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4656 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.33.0 > > > The code in the integration/artemis-spring-integration module has been > deprecated for over 6 years and indicates itself that it isnt even needed. It > seems essentially unused; one defunct project referenced it, and our sole > example that depends on the module doesnt actually even use it, having been > updated to use the embedded server several years ago like we recommend others > do in similar case. These days, Spring Boot and its related Artemis starter > also appear to be a more likely entry point in this space. > This change will update the Artemis spring-integration example to drop the > unused dep, and then remove the superfluous artemis-spring-integration module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4656) Remove superfluous artemis-spring-integration module
[ https://issues.apache.org/jira/browse/ARTEMIS-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4656. - Fix Version/s: 2.33.0 Resolution: Fixed > Remove superfluous artemis-spring-integration module > > > Key: ARTEMIS-4656 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4656 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Priority: Minor > Fix For: 2.33.0 > > > The code in the integration/artemis-spring-integration module has been > deprecated for over 6 years and indicates itself that it isnt even needed. It > seems essentially unused; one defunct project referenced it, and our sole > example that depends on the module doesnt actually even use it, having been > updated to use the embedded server several years ago like we recommend others > do in similar case. These days, Spring Boot and its related Artemis starter > also appear to be a more likely entry point in this space. > This change will update the Artemis spring-integration example to drop the > unused dep, and then remove the superfluous artemis-spring-integration module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4656) Remove superfluous artemis-spring-integration module
[ https://issues.apache.org/jira/browse/ARTEMIS-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821319#comment-17821319 ] Robbie Gemmell commented on ARTEMIS-4656: - Example updated in https://github.com/apache/activemq-artemis-examples/commit/328ca274d96c31a9c03705dad2f8bf6807a3f650 > Remove superfluous artemis-spring-integration module > > > Key: ARTEMIS-4656 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4656 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Priority: Minor > > The code in the integration/artemis-spring-integration module has been > deprecated for over 6 years and indicates itself that it isnt even needed. It > seems essentially unused; one defunct project referenced it, and our sole > example that depends on the module doesnt actually even use it, having been > updated to use the embedded server several years ago like we recommend others > do in similar case. These days, Spring Boot and its related Artemis starter > also appear to be a more likely entry point in this space. > This change will update the Artemis spring-integration example to drop the > unused dep, and then remove the superfluous artemis-spring-integration module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4656) Remove superfluous artemis-spring-integration module
Robbie Gemmell created ARTEMIS-4656: --- Summary: Remove superfluous artemis-spring-integration module Key: ARTEMIS-4656 URL: https://issues.apache.org/jira/browse/ARTEMIS-4656 Project: ActiveMQ Artemis Issue Type: Task Reporter: Robbie Gemmell The code in the integration/artemis-spring-integration module has been deprecated for over 6 years and indicates itself that it isnt even needed. It seems essentially unused; one defunct project referenced it, and our sole example that depends on the module doesnt actually even use it, having been updated to use the embedded server several years ago like we recommend others do in similar case. These days, Spring Boot and its related Artemis starter also appear to be a more likely entry point in this space. This change will update the Artemis spring-integration example to drop the unused dep, and then remove the superfluous artemis-spring-integration module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4653) AMQP Federation should apply queue consumer filters for demand
[ https://issues.apache.org/jira/browse/ARTEMIS-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4653. - Resolution: Fixed > AMQP Federation should apply queue consumer filters for demand > -- > > Key: ARTEMIS-4653 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4653 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: AMQP >Affects Versions: 2.32.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: 2.33.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > For Queue federation the federation consumers should apply a consumer defined > filter over the Queue defined filter to avoid pulling message across the link > that won't be deliverable. Add options for disabling this and also disabling > per consumer consumer priority tracking to allow for reduction of federation > links when desired. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4628) Upgrade vertx version to 4.5.3
[ https://issues.apache.org/jira/browse/ARTEMIS-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed ARTEMIS-4628. --- Removed fix-version since ARTEMIS-4644 removed the usage, so this change effectively 'wont be released'. > Upgrade vertx version to 4.5.3 > -- > > Key: ARTEMIS-4628 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4628 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4628) Upgrade vertx version to 4.5.3
[ https://issues.apache.org/jira/browse/ARTEMIS-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4628: Fix Version/s: (was: 2.33.0) > Upgrade vertx version to 4.5.3 > -- > > Key: ARTEMIS-4628 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4628 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4642) AMQP Federation demand tracking can under count demand in some narrow cases
[ https://issues.apache.org/jira/browse/ARTEMIS-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4642. - Resolution: Fixed > AMQP Federation demand tracking can under count demand in some narrow cases > --- > > Key: ARTEMIS-4642 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4642 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.32.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: 2.33.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In some narrow cases the AMQP federation demand tracking can under count the > demand on an address or queue and should track more closely the current > demand regardless of a federation link being active. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4644) convert some broker-connection tests to use test peer
[ https://issues.apache.org/jira/browse/ARTEMIS-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4644. - Resolution: Fixed > convert some broker-connection tests to use test peer > - > > Key: ARTEMIS-4644 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4644 > Project: ActiveMQ Artemis > Issue Type: Task > Components: AMQP >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.33.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Some of the AMQP Broker Connection tests utilise a vertx-proton based 'mock > server' to check the broker-connection behaviour. At the time they were added > these were really the first 'test server' based AMQP tests in the codebase. > Since then, a larger number of newer tests are now using the ProtonJ2 test > peer to handle such test verifications. We should convert the earlier tests > to use the same general approach. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4644) convert some broker-connection tests to use test peer
Robbie Gemmell created ARTEMIS-4644: --- Summary: convert some broker-connection tests to use test peer Key: ARTEMIS-4644 URL: https://issues.apache.org/jira/browse/ARTEMIS-4644 Project: ActiveMQ Artemis Issue Type: Task Components: AMQP Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.33.0 Some of the AMQP Broker Connection tests utilise a vertx-proton based 'mock server' to check the broker-connection behaviour. At the time they were added these were really the first 'test server' based AMQP tests in the codebase. Since then, a larger number of newer tests are now using the ProtonJ2 test peer to handle such test verifications. We should convert the earlier tests to use the same general approach. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ARTEMIS-1230) Create Maven Bill of Materials (BOM)
[ https://issues.apache.org/jira/browse/ARTEMIS-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened ARTEMIS-1230: - > Create Maven Bill of Materials (BOM) > > > Key: ARTEMIS-1230 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1230 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Daniel Siviter >Priority: Major > Time Spent: 7h > Remaining Estimate: 0h > > It's frustrating having to deal with dependency versions so the creation of a > Bill of Materials will assist with this. > I'm currently battling with Wildfly Swarm 2017.6.0 overriding to > v1.1.0.wildfly017. To override the version of Artemis I have to have an entry > in my POM for every single dependency which is arduous. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-1230) Create Maven Bill of Materials (BOM)
[ https://issues.apache.org/jira/browse/ARTEMIS-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-1230. - Fix Version/s: 2.33.0 Resolution: Fixed > Create Maven Bill of Materials (BOM) > > > Key: ARTEMIS-1230 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1230 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Daniel Siviter >Priority: Major > Fix For: 2.33.0 > > Time Spent: 7h > Remaining Estimate: 0h > > It's frustrating having to deal with dependency versions so the creation of a > Bill of Materials will assist with this. > I'm currently battling with Wildfly Swarm 2017.6.0 overriding to > v1.1.0.wildfly017. To override the version of Artemis I have to have an entry > in my POM for every single dependency which is arduous. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4628) Upgrade vertx version to 4.5.3
[ https://issues.apache.org/jira/browse/ARTEMIS-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4628. - Resolution: Fixed > Upgrade vertx version to 4.5.3 > -- > > Key: ARTEMIS-4628 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4628 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.33.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4641) Allow AMQP federation to recover from missing or removed resources
[ https://issues.apache.org/jira/browse/ARTEMIS-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4641. - Resolution: Fixed > Allow AMQP federation to recover from missing or removed resources > -- > > Key: ARTEMIS-4641 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4641 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: AMQP >Affects Versions: 2.32.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: 2.33.0 > > Time Spent: 50m > Remaining Estimate: 0h > > When an AMQP federation instance attempts to federate an address or queue it > can fail if the remote address or queue is not present or cannot be created > based on broker policy. A federation link can also closed if the federated > resource is removed from the remote broker by management etc. In those cases > the remote broker should note the resources that were targets of federation > and send alerts to the source federation broker to notify it that these > resources become available for federation and the source should attempt again > to create federation links if demand still exists. This allows an AMQP > federation instance to heal itself based on updates from the remote. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4639) Artemis Cluster and NullpointerException in "sending topology"
[
https://issues.apache.org/jira/browse/ARTEMIS-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-4639.
-
Fix Version/s: 2.33.0
Resolution: Fixed
> Artemis Cluster and NullpointerException in "sending topology"
> --
>
> Key: ARTEMIS-4639
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4639
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker, Clustering
>Affects Versions: 2.32.0
>Reporter: Jean-Pascal Briquet
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.33.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> A {{NullPointerException}} may appear while the "sending topology" operation
> is being executed.
> *Configuration:*
> Artemis clustering enabled with static connectors using the option
> {{{}allow-direct-connections-only="true"{}}}.
> *Broker logs:*
> {noformat}
> 2024-02-06 22:06:14,259 WARN [org.apache.activemq.artemis.core.client]
> AMQ212030: error sending topology
> java.lang.NullPointerException: Cannot invoke
> "org.apache.activemq.artemis.api.core.TransportConfiguration.newTransportConfig(String)"
> because the return value of
> "org.apache.activemq.artemis.api.core.client.TopologyMember.getLive()" is null
> at
> org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl.nodeUP(ClusterConnectionImpl.java:755)
> ~[artemis-server-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.client.impl.Topology$1.run(Topology.java:284)
> ~[artemis-core-client-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:57)
> ~[artemis-commons-2.30.0.jar:?]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:32)
> ~[artemis-commons-2.30.0.jar:?]
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:68)
> ~[artemis-commons-2.30.0.jar:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> [?:?]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> [artemis-commons-2.30.0.jar:?]
> 2024-02-06 22:06:14,260 WARN [org.apache.activemq.artemis.core.client]
> AMQ212030: error sending topology
> java.lang.NullPointerException: Cannot invoke
> "org.apache.activemq.artemis.api.core.TransportConfiguration.getParams()"
> because "liveConnector" is null
> at
> org.apache.activemq.artemis.core.client.impl.TopologyMemberImpl.toURI(TopologyMemberImpl.java:133)
> ~[artemis-core-client-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.generateMembersURI(OpenWireProtocolManager.java:536)
> ~[artemis-openwire-protocol-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.newConnectionControl(OpenWireProtocolManager.java:521)
> ~[artemis-openwire-protocol-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.updateClientClusterInfo(OpenWireProtocolManager.java:288)
> ~[artemis-openwire-protocol-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.nodeUP(OpenWireProtocolManager.java:236)
> ~[artemis-openwire-protocol-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.core.client.impl.Topology$1.run(Topology.java:284)
> ~[artemis-core-client-2.30.0.jar:2.30.0]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:57)
> ~[artemis-commons-2.30.0.jar:?]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:32)
> ~[artemis-commons-2.30.0.jar:?]
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:68)
> ~[artemis-commons-2.30.0.jar:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> [?:?]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> [artemis-commons-2.30.0.jar:?]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4640) move extension added to aid 'offline' maven usage into a profile
[ https://issues.apache.org/jira/browse/ARTEMIS-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4640. - Resolution: Fixed > move extension added to aid 'offline' maven usage into a profile > > > Key: ARTEMIS-4640 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4640 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.32.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.33.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The changes in ARTEMIS-4153 to broke the reproducibility of the > artemis-commons module build. The extension being present leads to > OS-specific properties being embedded in the published pom, e.g see > https://repo1.maven.org/maven2/org/apache/activemq/artemis-commons/2.32.0/artemis-commons-2.32.0.pom > The extension will be moved into a helper 'go-offline' profile so it can > still be used easily together with go-offline, even though its usefulness > actually seems limited. > Even after running dependency:go-offline with a clean local repo, the build > doesnt actually immediately work offline since that doesnt actually grab > everything needed at build time. You still need to run the build online to > get the added bits needed. > Instead, just running then normal build itself initially, it then does work > offline. > (Its also questionable if dependency:go-offline will actually be around in > future, a Jira was already raised to remove it due to various issues with it: > MDEP-904 ) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4638) Remove bashism from install validation script
[
https://issues.apache.org/jira/browse/ARTEMIS-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-4638.
-
Fix Version/s: 2.33.0
Resolution: Fixed
> Remove bashism from install validation script
> -
>
> Key: ARTEMIS-4638
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4638
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.33.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{validate-instalation.sh}} script in
> {{artemis-distribution/src/test/scripts/validate-instalation.sh}} specifies
> this shebang:
> {noformat}
> #!/usr/bin/env sh{noformat}
> However, it also uses the {{[[}} bashism which makes it fail on Debian based
> distributions (e.g. Ubuntu) since those distributions use
> [dash|https://en.wikipedia.org/wiki/Almquist_shell#dash] by default rather
> than bash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4640) move extension added to aid 'offline' maven usage into a profile
Robbie Gemmell created ARTEMIS-4640: --- Summary: move extension added to aid 'offline' maven usage into a profile Key: ARTEMIS-4640 URL: https://issues.apache.org/jira/browse/ARTEMIS-4640 Project: ActiveMQ Artemis Issue Type: Task Affects Versions: 2.32.0 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.33.0 The changes in ARTEMIS-4153 to broke the reproducibility of the artemis-commons module build. The extension being present leads to OS-specific properties being embedded in the published pom, e.g see https://repo1.maven.org/maven2/org/apache/activemq/artemis-commons/2.32.0/artemis-commons-2.32.0.pom The extension will be moved into a helper 'go-offline' profile so it can still be used easily together with go-offline, even though its usefulness actually seems limited. Even after running dependency:go-offline with a clean local repo, the build doesnt actually immediately work offline since that doesnt actually grab everything needed at build time. You still need to run the build online to get the added bits needed. Instead, just running then normal build itself initially, it then does work offline. (Its also questionable if dependency:go-offline will actually be around in future, a Jira was already raised to remove it due to various issues with it: MDEP-904 ) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4630) AMQ Service status is not validating if the pid is from Artemis
[ https://issues.apache.org/jira/browse/ARTEMIS-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4630. - Fix Version/s: 2.33.0 Resolution: Fixed > AMQ Service status is not validating if the pid is from Artemis > --- > > Key: ARTEMIS-4630 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4630 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Configuration >Affects Versions: 2.32.0 >Reporter: Angelo Galvão >Priority: Major > Fix For: 2.33.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > In a rare condition, an old artemis.pid file is pointing to an existing > process that is not Artemis, causing the provisioning tools to believe that > Artemis process is running. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4601) Remove OpenTelemetry deps from main pom
[ https://issues.apache.org/jira/browse/ARTEMIS-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813182#comment-17813182 ] Robbie Gemmell commented on ARTEMIS-4601: - The related earlier changes in the examples repo to add OpenTelemetry version config there where it is used (and also update things to version 1.34.1) was done in PR: [https://github.com/apache/activemq-artemis-examples/pull/4] > Remove OpenTelemetry deps from main pom > --- > > Key: ARTEMIS-4601 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4601 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4601) Remove OpenTelemetry deps from main pom
[ https://issues.apache.org/jira/browse/ARTEMIS-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4601. - Fix Version/s: 2.33.0 Resolution: Fixed > Remove OpenTelemetry deps from main pom > --- > > Key: ARTEMIS-4601 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4601 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.33.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4590) NPE after embedded server killed and restarted
[
https://issues.apache.org/jira/browse/ARTEMIS-4590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812597#comment-17812597
]
Robbie Gemmell commented on ARTEMIS-4590:
-
Looks to be the same breaking point as the initial report that was in
ARTEMIS-4540. That was resolved in 2.32.0, which released 1-2 hours before you
raised this issue, so you can give that a try now to see if it resolves things
for you.
> NPE after embedded server killed and restarted
> --
>
> Key: ARTEMIS-4590
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4590
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.31.2
>Reporter: Václav Haisman
>Priority: Major
> Attachments: image-2024-01-30-17-38-15-138.png
>
>
> I am having issues developing our application which contains embedded
> ActiveMQ Artemis server. If I start with empty data directory for Artemis
> server, everything goes smooth. Then I stop/kill the Spring Boot application
> in IntelliJ IDEA and restart it. Then, on the 2nd start, it ends up throwing
> NPE when it tries to put null client ID into a map.
> {code:java}
> 2024-01-30T17:34:05.987+01:00 WARN 12496 --- [ main]
> o.apache.activemq.artemis.core.server : AMQ222080: Error instantiating
> remoting acceptor
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactoryjava.lang.NullPointerException:
> null
> at
> java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
> at
> java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
> at
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTStateManager.(MQTTStateManager.java:88)
> at
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTStateManager.getInstance(MQTTStateManager.java:66)
> at
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTProtocolManager.(MQTTProtocolManager.java:86)
> at
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTProtocolManagerFactory.createProtocolManager(MQTTProtocolManagerFactory.java:51)
> at
> org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.createAcceptor(RemotingServiceImpl.java:271)
> at
> org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.start(RemotingServiceImpl.java:217)
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:3492)
> at
> org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:78)
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:720)
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:610)
> at
> org.apache.activemq.artemis.core.server.embedded.EmbeddedActiveMQ.start(EmbeddedActiveMQ.java:134)
> 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.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1872)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1825)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1764)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:596)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:518)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:325)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:323)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:663)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:651)
> at
>
[jira] [Resolved] (ARTEMIS-4589) consolidate utility code and remove test-jar usages within tests/ subtree
[ https://issues.apache.org/jira/browse/ARTEMIS-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4589. - Resolution: Fixed > consolidate utility code and remove test-jar usages within tests/ subtree > - > > Key: ARTEMIS-4589 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4589 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Tests >Affects Versions: 2.32.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.33.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Building on earlier work in ARTEMIS-3874 and ARTEMIS-4583 and other related > work, break the inter-dependency chains between lots of the modules within > the tests/ subtree and remove the remaining test-jar creations/uses that > facilitated it. Instead of this, consolidate test utility code/classes where > needed into the tests/artemis-test-support module (for use by any modules in > the tests/ tree, primarily for system/integration testing, and including > stuff that relies on the main Artemis build modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4589) consolidate utility code and remove test-jar usages within tests/ subtree
Robbie Gemmell created ARTEMIS-4589: --- Summary: consolidate utility code and remove test-jar usages within tests/ subtree Key: ARTEMIS-4589 URL: https://issues.apache.org/jira/browse/ARTEMIS-4589 Project: ActiveMQ Artemis Issue Type: Task Components: Tests Affects Versions: 2.32.0 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.33.0 Building on earlier work in ARTEMIS-3874 and ARTEMIS-4583 and other related work, break the inter-dependency chains between lots of the modules within the tests/ subtree and remove the remaining test-jar creations/uses that facilitated it. Instead of this, consolidate test utility code/classes where needed into the tests/artemis-test-support module (for use by any modules in the tests/ tree, primarily for system/integration testing, and including stuff that relies on the main Artemis build modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4533) Move the examples to their own repository
[ https://issues.apache.org/jira/browse/ARTEMIS-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812358#comment-17812358 ] Robbie Gemmell commented on ARTEMIS-4533: - ActiveMQ Artemis 2.32.0 had not been released yet when you posted (but did just complete its release vote a short time ago, after you posted, so its coming Real Soon Now) and so the examples repo has not yet been updated to use it, since it wouldn't work. When it is actually available, the examples repo will be updated to use it. If you cant wait, you can examine the development branch of the examples repo and try out ./scripts/update-examples-version.sh > Move the examples to their own repository > - > > Key: ARTEMIS-4533 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4533 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > Time Spent: 40m > Remaining Estimate: 0h > > As previously discussed > ([here|https://lists.apache.org/thread/jq783v0ywpgsnty6fw0n2nmxogjh935p]) the > examples will be moved to their own independent repository rather than being > part of the main Artemis repository and build. > The new examples repository will be: > [https://github.com/apache/activemq-artemis-examples/] > The examples repo _main_ branch will target the current Artemis release, with > changes toward/requiring the next release occurring on the _development_ > branch prior to the Artemis release happening. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4532) MQTT-to-core wildcard conversion is broken
[
https://issues.apache.org/jira/browse/ARTEMIS-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-4532.
-
Fix Version/s: 2.33.0
Resolution: Fixed
> MQTT-to-core wildcard conversion is broken
> --
>
> Key: ARTEMIS-4532
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4532
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.33.0
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> Currently when an MQTT topic filter contains characters from the configured
> [wildcard
> syntax|https://activemq.apache.org/components/artemis/documentation/latest/wildcard-syntax.html#wildcard-syntax]
> the conversion to/from this syntax breaks.
> For example, when using the default wildcard syntax if an MQTT topic filter
> contains a {{.}} the conversion from the MQTT wildcard syntax to the core
> wildcard syntax and back will result in the {{.}} being replaced with a {{/}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4550) Upgrade spring boot version to 2.7.18
[ https://issues.apache.org/jira/browse/ARTEMIS-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4550: Fix Version/s: 2.32.0 > Upgrade spring boot version to 2.7.18 > - > > Key: ARTEMIS-4550 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4550 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade > Components: ActiveMQ-Artemis-Examples >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.32.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4550) Upgrade spring boot version to 2.7.18
[ https://issues.apache.org/jira/browse/ARTEMIS-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4550. - Resolution: Fixed > Upgrade spring boot version to 2.7.18 > - > > Key: ARTEMIS-4550 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4550 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade > Components: ActiveMQ-Artemis-Examples >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.32.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4584) broker-connections TLS example reconnecting due to mismatched sender config
[ https://issues.apache.org/jira/browse/ARTEMIS-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4584: Component/s: ActiveMQ-Artemis-Examples > broker-connections TLS example reconnecting due to mismatched sender config > --- > > Key: ARTEMIS-4584 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4584 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Examples >Affects Versions: 2.31.2 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.32.0 > > > The broker-connection TLS example is repeatedly reconnecting due to > mismatched sender and security config. It is configured to create senders for > all queues via an address-match but only authorised for a specific queue the > example uses. It fouls on MQTT session state as a result (even though MQTT is > disabled; potential for improvement). It should be changed to just create a > sender for the specific queue used and actually authorised. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4551) Interceptor client example should not depend on interceptor example
[ https://issues.apache.org/jira/browse/ARTEMIS-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4551. - Fix Version/s: 2.32.0 Resolution: Fixed > Interceptor client example should not depend on interceptor example > --- > > Key: ARTEMIS-4551 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4551 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Examples >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.32.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The interceptor client example depends on the interceptor example. This > inter-dependence between them is not required and could cause the failure of > the check [verify > examples|https://github.com/apache/activemq-artemis-examples/blob/main/.github/workflows/build.yml]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4584) broker-connections TLS example reconnecting due to mismatched sender config
[ https://issues.apache.org/jira/browse/ARTEMIS-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4584. - Resolution: Fixed Resolved via https://github.com/apache/activemq-artemis-examples/commit/17e73558d629e6619c47d2ed72c0a2772d246edf > broker-connections TLS example reconnecting due to mismatched sender config > --- > > Key: ARTEMIS-4584 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4584 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.31.2 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 2.32.0 > > > The broker-connection TLS example is repeatedly reconnecting due to > mismatched sender and security config. It is configured to create senders for > all queues via an address-match but only authorised for a specific queue the > example uses. It fouls on MQTT session state as a result (even though MQTT is > disabled; potential for improvement). It should be changed to just create a > sender for the specific queue used and actually authorised. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4584) broker-connections TLS example reconnecting due to mismatched sender config
Robbie Gemmell created ARTEMIS-4584: --- Summary: broker-connections TLS example reconnecting due to mismatched sender config Key: ARTEMIS-4584 URL: https://issues.apache.org/jira/browse/ARTEMIS-4584 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.31.2 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.32.0 The broker-connection TLS example is repeatedly reconnecting due to mismatched sender and security config. It is configured to create senders for all queues via an address-match but only authorised for a specific queue the example uses. It fouls on MQTT session state as a result (even though MQTT is disabled; potential for improvement). It should be changed to just create a sender for the specific queue used and actually authorised. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4583) remove artemis-server module test-jar, do some related cleanup
[ https://issues.apache.org/jira/browse/ARTEMIS-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4583. - Resolution: Fixed > remove artemis-server module test-jar, do some related cleanup > -- > > Key: ARTEMIS-4583 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4583 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Tests >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.33.0 > > Time Spent: 1h > Remaining Estimate: 0h > > The tests/ subtree of the repo has lots of modules that create a chain of > test module dependencies back to the test-jar created artemis-server module, > mostly in order to get at the ActiveMQTestBase support class and other helper > rules etc. This class is overly complex for the tests in the artemis-server > module, with most (~2000 lines) of it unused there and instead actually aimed > at system tests that are in the integration-tests, smoke-tests, etc etc > modules. We can improve (and eventually speed up) the build by simplifying > things and breaking such chains, while moving support code into either the > artemis-unit-test module (for use by any module in the codebase) that now > exists, or the even older artemis-test-support module (for use in any system > tests in the tests/ subtree). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4583) remove artemis-server module test-jar, do some related cleanup
Robbie Gemmell created ARTEMIS-4583: --- Summary: remove artemis-server module test-jar, do some related cleanup Key: ARTEMIS-4583 URL: https://issues.apache.org/jira/browse/ARTEMIS-4583 Project: ActiveMQ Artemis Issue Type: Task Components: Tests Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.33.0 The tests/ subtree of the repo has lots of modules that create a chain of test module dependencies back to the test-jar created artemis-server module, mostly in order to get at the ActiveMQTestBase support class and other helper rules etc. This class is overly complex for the tests in the artemis-server module, with most (~2000 lines) of it unused there and instead actually aimed at system tests that are in the integration-tests, smoke-tests, etc etc modules. We can improve (and eventually speed up) the build by simplifying things and breaking such chains, while moving support code into either the artemis-unit-test module (for use by any module in the codebase) that now exists, or the even older artemis-test-support module (for use in any system tests in the tests/ subtree). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4567) Support OpenWire clients for broker embedded in Jakarta environment
[
https://issues.apache.org/jira/browse/ARTEMIS-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-4567.
-
Fix Version/s: 2.32.0
Resolution: Fixed
> Support OpenWire clients for broker embedded in Jakarta environment
> ---
>
> Key: ARTEMIS-4567
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4567
> Project: ActiveMQ Artemis
> Issue Type: Task
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> If the broker is embedded into a Jakarta environment (e.g. Spring Boot 3.x)
> then the existing {{artemis-openwire-protocol}} module won't work because it
> uses {{javax}} classes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4578) Upgrade Jackson to 2.16.1
[ https://issues.apache.org/jira/browse/ARTEMIS-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4578. - Fix Version/s: 2.32.0 Resolution: Fixed > Upgrade Jackson to 2.16.1 > - > > Key: ARTEMIS-4578 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4578 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4552) Configure all connection-router settings by using broker properties
[
https://issues.apache.org/jira/browse/ARTEMIS-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-4552.
-
Fix Version/s: 2.32.0
Resolution: Fixed
> Configure all connection-router settings by using broker properties
> ---
>
> Key: ARTEMIS-4552
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4552
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Domenico Francesco Bruscino
>Assignee: Domenico Francesco Bruscino
>Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Allow to configure all the connection-router settings by using the broker
> properties. The broker properties for the cache configuration cause a null
> pointer exception:
> {code}
> "connectionRouters.autoShard.cacheConfiguration.persisted=true"
> "connectionRouters.autoShard.cacheConfiguration.timeout=6"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4572) Upgrade to Apache parent 31
[ https://issues.apache.org/jira/browse/ARTEMIS-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4572. - Fix Version/s: 2.32.0 Resolution: Fixed > Upgrade to Apache parent 31 > --- > > Key: ARTEMIS-4572 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4572 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4573) Upgrade Checkstyle to 10.12.7 & Sevntu to 1.44.1
[ https://issues.apache.org/jira/browse/ARTEMIS-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4573. - Fix Version/s: 2.32.0 Resolution: Fixed > Upgrade Checkstyle to 10.12.7 & Sevntu to 1.44.1 > > > Key: ARTEMIS-4573 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4573 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4556) Support release of multi-platform Docker images
[
https://issues.apache.org/jira/browse/ARTEMIS-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-4556.
-
Fix Version/s: 2.32.0
Resolution: Fixed
> Support release of multi-platform Docker images
> ---
>
> Key: ARTEMIS-4556
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4556
> Project: ActiveMQ Artemis
> Issue Type: Task
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> We currently release Docker images only for {{{}linux/amd64{}}}, but images
> can be [built supporting multiple
> platforms|https://docs.docker.com/build/building/multi-platform/]. However,
> whatever platforms we choose to build must be supported by the based images
> we use. We currently publish images using:
> * [Eclipse Temurin Java 21 JRE based on
> Ubuntu|https://hub.docker.com/layers/library/eclipse-temurin/21-jre/images/sha256-2d00f6910282a7a20ae7747b8f5e2371f7d55f06daed6bf60a323fcc7eaa3da8?context=explore]
> * [Eclipse Temurin Java 21 JRE based on
> Alpine|https://hub.docker.com/layers/library/eclipse-temurin/21-jre-alpine/images/sha256-98963ed09c4fd82e128c6cc9e64d71798239b824164276626d79b8f9e666ac0e?context=explore]
> Both of these images support:
> * {{linux/amd64}}
> * {{linux/arm64}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4548) Refactor MQTT tests
[ https://issues.apache.org/jira/browse/ARTEMIS-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4548. - Fix Version/s: 2.32.0 Resolution: Fixed > Refactor MQTT tests > --- > > Key: ARTEMIS-4548 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4548 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Many MQTT tests are run twice - once using TCP and once using WebSockets. > This is essentially a big waste of time since once the connection is > established to the broker the tests are identical. The tests should be > refactored to run just once and then there can be a small number of tests > specifically for WebSockets. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4563) Auto created addresses are not removed upon restart
[ https://issues.apache.org/jira/browse/ARTEMIS-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4563. - Fix Version/s: 2.32.0 Resolution: Fixed > Auto created addresses are not removed upon restart > --- > > Key: ARTEMIS-4563 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4563 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.32.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Auto created addresses without queues are not removed upon restart after > upgrading to 2.29.0 or any later versions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4554) Upgrade to latest Java for Docker images
[ https://issues.apache.org/jira/browse/ARTEMIS-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4554. - Fix Version/s: 2.32.0 Resolution: Fixed > Upgrade to latest Java for Docker images > - > > Key: ARTEMIS-4554 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4554 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 2h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4539) simplify various release process steps
[ https://issues.apache.org/jira/browse/ARTEMIS-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799073#comment-17799073 ] Robbie Gemmell commented on ARTEMIS-4539: - The first 4 commits add specific scripts to do various component steps of the website updates (creating git report, release-notes, release collection file, and copying docs+javadocs from the artemis release build). These can all be called individually (git-report usually being created pre-vote), however the last commit above adds another script that calls all the others (skips git-report if found to be present already,as it should be) such that the bulk of the post-vote website updates can all now be done with that single script call. > simplify various release process steps > -- > > Key: ARTEMIS-4539 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4539 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > > There are currently a lot of manual steps during the release process that > involve running various commands from the RELEASING.md document, with various > c generally involved. They aren't difficult steps, but it does make the > process more cumbersome, fragile, and significantly slower than it need > actually be. We can script various aspects of the updates so just some simple > easily-remembered/discovered commands can be run to do most of the work, > simplifying the release process and making it much less of a chore to > actually do releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4539) simplify various release process steps
[ https://issues.apache.org/jira/browse/ARTEMIS-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4539. - Resolution: Fixed > simplify various release process steps > -- > > Key: ARTEMIS-4539 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4539 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > > There are currently a lot of manual steps during the release process that > involve running various commands from the RELEASING.md document, with various > c generally involved. They aren't difficult steps, but it does make the > process more cumbersome, fragile, and significantly slower than it need > actually be. We can script various aspects of the updates so just some simple > easily-remembered/discovered commands can be run to do most of the work, > simplifying the release process and making it much less of a chore to > actually do releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4541) Clarify divert docs
[ https://issues.apache.org/jira/browse/ARTEMIS-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4541. - Fix Version/s: 2.32.0 Resolution: Fixed > Clarify divert docs > --- > > Key: ARTEMIS-4541 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4541 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4500) Upgrade Netty to 4.1.101.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4500. - Resolution: Fixed > Upgrade Netty to 4.1.101.Final > -- > > Key: ARTEMIS-4500 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4500 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Emmanuel Hugonnet >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4500) Upgrade Netty to 4.1.101.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4500: Fix Version/s: 2.32.0 (was: 2.30.0) > Upgrade Netty to 4.1.101.Final > -- > > Key: ARTEMIS-4500 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4500 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Emmanuel Hugonnet >Assignee: Justin Bertram >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4538) Make note around amqp broker-connection URI transport options more prominent
[
https://issues.apache.org/jira/browse/ARTEMIS-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-4538.
-
Fix Version/s: 2.32.0
Resolution: Fixed
I updated things so the existing note about configuring transport options for
TLS, with pointers to related options page and example, now use the 'alert
style' note so it is more prominent.
> Make note around amqp broker-connection URI transport options more prominent
>
>
> Key: ARTEMIS-4538
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4538
> Project: ActiveMQ Artemis
> Issue Type: Task
>Reporter: John Clifford
>Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 2.32.0
>
>
> Make existing note around amqp-broker-connection URI transport options, such
> as for enabling and configuring TLS, more prominent.
>
> ===
> Original Description:
> The [Artemis
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html]
> explains how to make a connection for mirroring using the
> {{}} configuration. However, it isn't clear what format the
> connection URI takes. In particularly, it isn't clear how to configure it to
> use TLS.
> I understand that the URI format is, in fact, the same as that used by other
> Artemis network connections. I would not have guessed this, because Artemis
> does not use AMQP for any of these other connections, and I just assumed that
> AMQP mirroring connections would be configured differently.
> So I think all that is needed here is one additional line explaining this,
> and perhaps linking to the relevant section of the docs. A specific example
> of configuring a mirror connection using TLS would, I think, provide useful
> additional help.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (ARTEMIS-4538) Make note around amqp broker-connection URI transport options more prominent
[
https://issues.apache.org/jira/browse/ARTEMIS-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reassigned ARTEMIS-4538:
---
Assignee: Robbie Gemmell
Description:
Make existing note around amqp-broker-connection URI transport options, such as
for enabling and configuring TLS, more prominent.
===
Original Description:
The [Artemis
documentation|https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html]
explains how to make a connection for mirroring using the
{{}} configuration. However, it isn't clear what format the
connection URI takes. In particularly, it isn't clear how to configure it to
use TLS.
I understand that the URI format is, in fact, the same as that used by other
Artemis network connections. I would not have guessed this, because Artemis
does not use AMQP for any of these other connections, and I just assumed that
AMQP mirroring connections would be configured differently.
So I think all that is needed here is one additional line explaining this, and
perhaps linking to the relevant section of the docs. A specific example of
configuring a mirror connection using TLS would, I think, provide useful
additional help.
was:
The [Artemis
documentation|https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html]
explains how to make a connection for mirroring using the
{{}} configuration. However, it isn't clear what format the
connection URI takes. In particularly, it isn't clear how to configure it to
use TLS.
I understand that the URI format is, in fact, the same as that used by other
Artemis network connections. I would not have guessed this, because Artemis
does not use AMQP for any of these other connections, and I just assumed that
AMQP mirroring connections would be configured differently.
So I think all that is needed here is one additional line explaining this, and
perhaps linking to the relevant section of the docs. A specific example of
configuring a mirror connection using TLS would, I think, provide useful
additional help.
Summary: Make note around amqp broker-connection URI transport options
more prominent (was: Update mirroring documentation to clarify format of
mirroring connection URIs)
> Make note around amqp broker-connection URI transport options more prominent
>
>
> Key: ARTEMIS-4538
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4538
> Project: ActiveMQ Artemis
> Issue Type: Task
>Reporter: John Clifford
>Assignee: Robbie Gemmell
>Priority: Major
>
> Make existing note around amqp-broker-connection URI transport options, such
> as for enabling and configuring TLS, more prominent.
>
> ===
> Original Description:
> The [Artemis
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html]
> explains how to make a connection for mirroring using the
> {{}} configuration. However, it isn't clear what format the
> connection URI takes. In particularly, it isn't clear how to configure it to
> use TLS.
> I understand that the URI format is, in fact, the same as that used by other
> Artemis network connections. I would not have guessed this, because Artemis
> does not use AMQP for any of these other connections, and I just assumed that
> AMQP mirroring connections would be configured differently.
> So I think all that is needed here is one additional line explaining this,
> and perhaps linking to the relevant section of the docs. A specific example
> of configuring a mirror connection using TLS would, I think, provide useful
> additional help.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4538) Update mirroring documentation to clarify format of mirroring connection URIs
[
https://issues.apache.org/jira/browse/ARTEMIS-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17797259#comment-17797259
]
Robbie Gemmell commented on ARTEMIS-4538:
-
The reference may not have existed at that time. I dont think it really makes
sense to add something to the mirroring section specifically, when its already
covered by the initial general section covering configuring a broker-connection
at all, including the URL. Would we than also add it to the 4 other connection
sub-element types, given the mirroring one is no different than the other 4 in
this regard? I dont see that making sense. This is already just pointing out it
is configured the same way this stuff is everywhere else in the broker, when
nothing has been said to suggest otherwise. Once seems enough.
> Update mirroring documentation to clarify format of mirroring connection URIs
> -
>
> Key: ARTEMIS-4538
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4538
> Project: ActiveMQ Artemis
> Issue Type: Task
>Reporter: John Clifford
>Priority: Major
>
> The [Artemis
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html]
> explains how to make a connection for mirroring using the
> {{}} configuration. However, it isn't clear what format the
> connection URI takes. In particularly, it isn't clear how to configure it to
> use TLS.
> I understand that the URI format is, in fact, the same as that used by other
> Artemis network connections. I would not have guessed this, because Artemis
> does not use AMQP for any of these other connections, and I just assumed that
> AMQP mirroring connections would be configured differently.
> So I think all that is needed here is one additional line explaining this,
> and perhaps linking to the relevant section of the docs. A specific example
> of configuring a mirror connection using TLS would, I think, provide useful
> additional help.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work started] (ARTEMIS-4539) simplify various release process steps
[ https://issues.apache.org/jira/browse/ARTEMIS-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-4539 started by Robbie Gemmell. --- > simplify various release process steps > -- > > Key: ARTEMIS-4539 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4539 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.32.0 > > > There are currently a lot of manual steps during the release process that > involve running various commands from the RELEASING.md document, with various > c generally involved. They aren't difficult steps, but it does make the > process more cumbersome, fragile, and significantly slower than it need > actually be. We can script various aspects of the updates so just some simple > easily-remembered/discovered commands can be run to do most of the work, > simplifying the release process and making it much less of a chore to > actually do releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4539) simplify various release process steps
Robbie Gemmell created ARTEMIS-4539: --- Summary: simplify various release process steps Key: ARTEMIS-4539 URL: https://issues.apache.org/jira/browse/ARTEMIS-4539 Project: ActiveMQ Artemis Issue Type: Task Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.32.0 There are currently a lot of manual steps during the release process that involve running various commands from the RELEASING.md document, with various c generally involved. They aren't difficult steps, but it does make the process more cumbersome, fragile, and significantly slower than it need actually be. We can script various aspects of the updates so just some simple easily-remembered/discovered commands can be run to do most of the work, simplifying the release process and making it much less of a chore to actually do releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4538) Update mirroring documentation to clarify format of mirroring connection URIs
[
https://issues.apache.org/jira/browse/ARTEMIS-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17797239#comment-17797239
]
Robbie Gemmell edited comment on ARTEMIS-4538 at 12/15/23 4:21 PM:
---
The documentation has a specific note already that the TLS config for broker
connections is in fact not configured differently than any other broker TLS
connection config, just in case anyone should assume they were for $reasons I
dont understand. There is also already a specific example referenced showing
how to configure TLS for an amqp broker connection:
[https://github.com/apache/activemq-artemis-examples/tree/main/examples/features/broker-connection/amqp-sending-overssl.]
[https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html#amqp-server-connections]
"Note that the connection URI options for transport settings such as enabling
and configuring TLS are common with other Artemis connector URIs. See [the
transport
doc|https://activemq.apache.org/components/artemis/documentation/latest/configuring-transports.html#configuring-netty-ssl]
for more. An example configuration for a TLS AMQP broker-connection can be
found in the broker examples at
./examples/features/broker-connection/amqp-sending-overssl."
(The example reference could be updated for 2.32.0 to point to the new examples
repo, I'll take of that under ARTEMIS-4533)
was (Author: gemmellr):
The documentation has a specific note already that the TLS config for broker
connections is in fact not configured differently than any other broker TLS
connection config, just in case anyone should assume they were for $reasons I
dont understand. There is also already a specific example showing how to
configure TLS for an amqp broker connection:
[https://github.com/apache/activemq-artemis-examples/tree/main/examples/features/broker-connection/amqp-sending-overssl.]
https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html#amqp-server-connections
"Note that the connection URI options for transport settings such as enabling
and configuring TLS are common with other Artemis connector URIs. See [the
transport
doc|https://activemq.apache.org/components/artemis/documentation/latest/configuring-transports.html#configuring-netty-ssl]
for more. An example configuration for a TLS AMQP broker-connection can be
found in the broker examples at
./examples/features/broker-connection/amqp-sending-overssl.
(The example reference could be updated for 2.32.0 to point to the new examples
repo, I'll take of that under ARTEMIS-4533)
> Update mirroring documentation to clarify format of mirroring connection URIs
> -
>
> Key: ARTEMIS-4538
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4538
> Project: ActiveMQ Artemis
> Issue Type: Task
>Reporter: John Clifford
>Priority: Major
>
> The [Artemis
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html]
> explains how to make a connection for mirroring using the
> {{}} configuration. However, it isn't clear what format the
> connection URI takes. In particularly, it isn't clear how to configure it to
> use TLS.
> I understand that the URI format is, in fact, the same as that used by other
> Artemis network connections. I would not have guessed this, because Artemis
> does not use AMQP for any of these other connections, and I just assumed that
> AMQP mirroring connections would be configured differently.
> So I think all that is needed here is one additional line explaining this,
> and perhaps linking to the relevant section of the docs. A specific example
> of configuring a mirror connection using TLS would, I think, provide useful
> additional help.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
