[jira] [Work logged] (ARTEMIS-4541) Clarify divert docs
[ https://issues.apache.org/jira/browse/ARTEMIS-4541?focusedWorklogId=896171=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-896171 ] ASF GitHub Bot logged work on ARTEMIS-4541: --- Author: ASF GitHub Bot Created on: 19/Dec/23 03:03 Start Date: 19/Dec/23 03:03 Worklog Time Spent: 10m Work Description: jbertram opened a new pull request, #4717: URL: https://github.com/apache/activemq-artemis/pull/4717 (no comment) Issue Time Tracking --- Worklog Id: (was: 896171) Remaining Estimate: 0h Time Spent: 10m > 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 > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4541) Clarify divert docs
Justin Bertram created ARTEMIS-4541: --- Summary: 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 -- 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=17798292#comment-17798292 ] ASF subversion and git services commented on ARTEMIS-4539: -- Commit 69e3a1a8a06cb0e36864e5d046c7ae8de95d102c in activemq-artemis's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=69e3a1a8a0 ] ARTEMIS-4539: update steps for creating release colletion file, simplify to just using script in website repo - Initial script added in website repo commit https://github.com/apache/activemq-website/commit/0851d833824ab4689d0c5781e7c656f7ba31e869 > 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] [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=17798254#comment-17798254 ] ASF subversion and git services commented on ARTEMIS-4539: -- Commit bd658bedc3cfbcedd4152fa3e7f2bac18fad372d in activemq-artemis's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=bd658bedc3 ] ARTEMIS-4539: update steps for creating release notes, simplify to just using script in website repo - Initial script added in website repo commit https://github.com/apache/activemq-website/commit/74e914b1788a3958fff01d1c8b26b7bcc1fd6ad3 > 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] [Commented] (ARTEMIS-3932) replace addAddressSettings with JSON param
[ https://issues.apache.org/jira/browse/ARTEMIS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798243#comment-17798243 ] ASF subversion and git services commented on ARTEMIS-3932: -- Commit 177e566f7591a53c1ab4b6496edc02deb5852568 in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=177e566f75 ] ARTEMIS-3932 Move meta bean init to static blocks > replace addAddressSettings with JSON param > -- > > Key: ARTEMIS-3932 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3932 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.31.2 >Reporter: Andy Taylor >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.32.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Similar to what we did with createQueue deprecate the addAddressSettings in > ServerControl and add a json version -- 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] [Created] (ARTEMIS-4540) NullPointerException during initialization
Daniel Martin created ARTEMIS-4540:
--
Summary: NullPointerException during initialization
Key: ARTEMIS-4540
URL: https://issues.apache.org/jira/browse/ARTEMIS-4540
Project: ActiveMQ Artemis
Issue Type: Bug
Reporter: Daniel Martin
{noformat}
__ _
/ \ | |_ ___ __ __(_) _
/ _ \| _ \ __|/ _ \ \/ | |/ __/
/ ___ \ | \/ |_/ __/ |\/| | |\___ \
/_/ \_\| \__\|_| |_|_|/___ /
Apache ActiveMQ Artemis 2.31.0
18:58:47,218 INFO [org.apache.activemq.artemis.integration.bootstrap]
AMQ101000: Starting ActiveMQ Artemis Server version 2.31.0
18:58:47,288 INFO [org.apache.activemq.artemis.core.server] AMQ221000: live
Message Broker is starting with configuration Broker Configuration
(clustered=false,journalDirectory=data/journal,bindingsDirectory=data/bindings,largeMessagesDirectory=data/large-messages,pagingDirectory=data/paging)
18:58:47,371 INFO [org.apache.activemq.artemis.core.server] AMQ221013: Using
NIO Journal
18:58:47,475 INFO [org.apache.activemq.artemis.core.server] AMQ221057: Global
Max Size is being adjusted to 1/2 of the JVM max size (-Xmx). being defined as
1073741824
18:58:47,522 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-server]. Adding protocol support for: CORE
18:58:47,524 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-amqp-protocol]. Adding protocol support for:
AMQP
18:58:47,524 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for:
HORNETQ
18:58:47,528 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-mqtt-protocol]. Adding protocol support for:
MQTT
18:58:47,528 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-openwire-protocol]. Adding protocol support
for: OPENWIRE
18:58:47,528 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-stomp-protocol]. Adding protocol support for:
STOMP
18:58:47,664 INFO [org.apache.activemq.artemis.core.server] AMQ221034: Waiting
indefinitely to obtain live lock
18:58:47,664 INFO [org.apache.activemq.artemis.core.server] AMQ221035: Live
Server Obtained live lock
18:58:48,822 INFO [org.apache.activemq.artemis.core.server] AMQ221080:
Deploying address DLQ supporting [ANYCAST]
18:58:48,823 INFO [org.apache.activemq.artemis.core.server] AMQ221003:
Deploying ANYCAST queue DLQ on address DLQ
18:58:48,833 INFO [org.apache.activemq.artemis.core.server] AMQ221080:
Deploying address ExpiryQueue supporting [ANYCAST]
18:58:48,834 INFO [org.apache.activemq.artemis.core.server] AMQ221003:
Deploying ANYCAST queue ExpiryQueue on address ExpiryQueue
18:58:49,081 WARN [org.apache.activemq.artemis.core.server] AMQ222080: Error
instantiating remoting acceptor
org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactory
java.lang.NullPointerException: null
at
java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
~[?:?]
at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
~[?:?]
at
org.apache.activemq.artemis.core.protocol.mqtt.MQTTStateManager.(MQTTStateManager.java:88)
~[artemis-mqtt-protocol-2.31.0.jar:2.31.0]
at
org.apache.activemq.artemis.core.protocol.mqtt.MQTTStateManager.getInstance(MQTTStateManager.java:66)
~[artemis-mqtt-protocol-2.31.0.jar:2.31.0]
at
org.apache.activemq.artemis.core.protocol.mqtt.MQTTProtocolManager.(MQTTProtocolManager.java:86)
~[artemis-mqtt-protocol-2.31.0.jar:2.31.0]
at
org.apache.activemq.artemis.core.protocol.mqtt.MQTTProtocolManagerFactory.createProtocolManager(MQTTProtocolManagerFactory.java:51)
~[artemis-mqtt-protocol-2.31.0.jar:2.31.0]
at
org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.createAcceptor(RemotingServiceImpl.java:271)
[artemis-server-2.31.0.jar:2.31.0]
at
org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.start(RemotingServiceImpl.java:217)
[artemis-server-2.31.0.jar:2.31.0]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:3488)
[artemis-server-2.31.0.jar:2.31.0]
at
org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:78)
[artemis-server-2.31.0.jar:2.31.0]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:720)
[artemis-server-2.31.0.jar:2.31.0]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:610)
[artemis-server-2.31.0.jar:2.31.0]
at
org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:66)
[artemis-cli-2.31.0.jar:2.31.0]
at
[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] [Commented] (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:comment-tabpanel=17798173#comment-17798173
]
ASF subversion and git services commented on ARTEMIS-4538:
--
Commit bbfd0f8e15fccfd4691b4a869b907d1d542dbc8a in activemq-artemis's branch
refs/heads/main from Robbie Gemmell
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=bbfd0f8e15 ]
ARTEMIS-4538: use the 'alert style NOTE' to make existing detail stand out
more, in common with the ones that follow
> 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] [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-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=17798162#comment-17798162 ] ASF subversion and git services commented on ARTEMIS-4533: -- Commit b0f817e89877e8fe59f8e35d157c0cac37fc6098 in activemq-artemis's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=b0f817e898 ] ARTEMIS-4533: some fixups, cleanups, and linking more bits to the examples page of docs > 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] [Work logged] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=896049=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-896049 ] ASF GitHub Bot logged work on ARTEMIS-4498: --- Author: ASF GitHub Bot Created on: 18/Dec/23 10:55 Start Date: 18/Dec/23 10:55 Worklog Time Spent: 10m Work Description: AntonRoskvist commented on PR #4670: URL: https://github.com/apache/activemq-artemis/pull/4670#issuecomment-1860136459 @jbertram This should address the issues you noted. In addition I also set the `MQTT_SESSION_STORE` as "non manageable" since that is the destination that caused a few of the previous tests to fail (it always gets created if the broker starts with the mqtt-module enabled). Consequently, I reverted the changes made to `queueMetrics.groovy` because they are no longer needed. Issue Time Tracking --- Worklog Id: (was: 896049) Time Spent: 5h (was: 4h 50m) > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 5h > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
