This is an automated email from the ASF dual-hosted git repository.
robbie pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/artemis.git
The following commit(s) were added to refs/heads/main by this push:
new b3d97de325 ARTEMIS-5807: more doc updates around new TLP
b3d97de325 is described below
commit b3d97de325eca1e14fdadd7109b55c1a6ab8c8ec
Author: Robbie Gemmell <[email protected]>
AuthorDate: Tue Dec 23 13:31:53 2025 +0000
ARTEMIS-5807: more doc updates around new TLP
---
docs/hacking-guide/_building.adoc | 4 +-
docs/hacking-guide/_code.adoc | 24 ++---
docs/hacking-guide/_validating-releases.adoc | 35 +++----
docs/user-manual/configuring-transports.adoc | 34 +++----
docs/user-manual/docker.adoc | 2 +-
docs/user-manual/examples.adoc | 147 +++++++++++++--------------
docs/user-manual/ha.adoc | 4 +-
docs/user-manual/karaf.adoc | 12 +--
docs/user-manual/management-console.adoc | 4 +-
docs/user-manual/management.adoc | 4 +-
docs/user-manual/message-grouping.adoc | 2 +-
docs/user-manual/network-isolation.adoc | 4 +-
docs/user-manual/upgrading.adoc | 3 +-
docs/user-manual/using-cli.adoc | 18 ++--
docs/user-manual/versions.adoc | 6 +-
15 files changed, 144 insertions(+), 159 deletions(-)
diff --git a/docs/hacking-guide/_building.adoc
b/docs/hacking-guide/_building.adoc
index 54608dadf2..02e3eeda86 100644
--- a/docs/hacking-guide/_building.adoc
+++ b/docs/hacking-guide/_building.adoc
@@ -86,6 +86,6 @@ The output for every module will be aggregated in
`./target/dependency-check-rep
== Snapshot Builds
-Snapshot builds are available at
https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-artemis/.
+Snapshot builds are available at
https://repository.apache.org/content/repositories/snapshots/org/apache/artemis/apache-artemis/.
-These are built by
https://ci-builds.apache.org/job/ActiveMQ/job/ActiveMQ-Artemis-SNAPSHOT-Deploy/[this
Apache CI job].
+These are built by
https://ci-builds.apache.org/job/Artemis/job/Artemis-SNAPSHOT-Deploy/[this
Apache CI job].
diff --git a/docs/hacking-guide/_code.adoc b/docs/hacking-guide/_code.adoc
index bab365c8ff..2d5ce3263c 100644
--- a/docs/hacking-guide/_code.adoc
+++ b/docs/hacking-guide/_code.adoc
@@ -43,22 +43,18 @@ For example:
+
[,sh]
----
-$ mvn -Pdev install
+$ mvn -Pdev install -DskipTests
...
[INFO] ------------------------------------------------------------------------
-[INFO] Reactor Summary:
+[INFO] Reactor Summary for Apache Artemis <VERSION>-SNAPSHOT:
[INFO]
-[INFO] ActiveMQ Artemis Parent ........................... SUCCESS [2.298s]
-[INFO] ActiveMQ Artemis Commons .......................... SUCCESS [1.821s]
-[INFO] ActiveMQ Artemis Selector Implementation .......... SUCCESS [0.767s]
-[INFO] ActiveMQ Artemis Native POM ....................... SUCCESS [0.189s]
-[INFO] ActiveMQ Artemis Journal .......................... SUCCESS [0.646s]
-[INFO] ActiveMQ Artemis Core Client ...................... SUCCESS [5.969s]
-[INFO] ActiveMQ Artemis JMS Client ....................... SUCCESS [2.110s]
-[INFO] ActiveMQ Artemis Server ........................... SUCCESS [11.540s]
-...
-[INFO] ActiveMQ Artemis stress Tests ..................... SUCCESS [0.332s]
-[INFO] ActiveMQ Artemis performance Tests ................ SUCCESS [0.174s]
+[INFO] Apache Artemis ..................................... SUCCESS [ 2.435 s]
+[INFO] Apache Artemis Bill of Materials ................... SUCCESS [ 0.094 s]
+...etc...
+[INFO] Apache Artemis Server .............................. SUCCESS [ 11.866 s]
+...etc...
+[INFO] Apache Artemis JMS Client .......................... SUCCESS [ 1.036 s]
+...etc...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
@@ -139,7 +135,7 @@ Therefore you'll want to make sure that you either work in
a branch that you do
. Get your changes merged into upstream
.. Send a GitHub pull request, by clicking the pull request link while in your
repo's fork.
-.. An email will automatically be sent to the ActiveMQ developer list.
+.. An email will automatically be sent to the Artemis issues mailing list.
.. As part of the review you may see an automated test run comment on your
request.
.. After review a maintainer will merge your PR into the canonical git
repository at which point those changes will be synced with the GitHub mirror
repository (i.e. your `main`) and your PR will be closed by the `asfgit` bot.
diff --git a/docs/hacking-guide/_validating-releases.adoc
b/docs/hacking-guide/_validating-releases.adoc
index 06b11cef53..7510212363 100644
--- a/docs/hacking-guide/_validating-releases.adoc
+++ b/docs/hacking-guide/_validating-releases.adoc
@@ -6,10 +6,10 @@ When a release is proposed a maven repository is staged.
This information was extracted from
https://maven.apache.org/guides/development/guide-testing-releases.html[Guide
to Testing Staged Releases]
-For examples, the 1.1.0 release had the Maven Repository staged as
https://repository.apache.org/content/repositories/orgapacheactivemq-1066.
+An example staging repository created during the release process would be:
https://repository.apache.org/content/repositories/orgapacheartemis-1002.
-The first thing you need to do is to be able to use this release.
-The easiest way we have found is to change your maven settings at
`~/.m2/settings.xml`, setting up the staged repo.
+The first thing you need to do is to be able to access this staging repository.
+The easiest way we have found is to change your maven settings at
`~/.m2/settings.xml`, setting up the staging repo.
[,xml]
.~/.m2/settings.xml
@@ -18,32 +18,32 @@ The easiest way we have found is to change your maven
settings at `~/.m2/setting
<settings>
<profiles>
<profile>
- <id>activemq-artemis-test</id>
+ <id>apache-artemis-staging</id>
<repositories>
<repository>
- <id>artemis-test</id>
- <name>ActiveMQ Artemis Test</name>
-
<url>https://repository.apache.org/content/repositories/orgapacheactivemq-1066</url>
+ <id>artemis-staging</id>
+ <name>Apache Artemis Staging</name>
+
<url>https://repository.apache.org/content/repositories/orgapacheartemis-1002</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
- <enabled>true</enabled>
+ <enabled>false</enabled>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
- <id>artemis-test2</id>
- <name>ActiveMQ Artemis Test</name>
-
<url>https://repository.apache.org/content/repositories/orgapacheactivemq-1066</url>
+ <id>artemis-staging</id>
+ <name>Apache Artemis Staging</name>
+
<url>https://repository.apache.org/content/repositories/orgapacheartemis-1002</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
- <enabled>true</enabled>
+ <enabled>false</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
@@ -51,16 +51,9 @@ The easiest way we have found is to change your maven
settings at `~/.m2/setting
</profiles>
<activeProfiles>
- <activeProfile>activemq-artemis-test</activeProfile>
+ <activeProfile>apache-artemis-staging</activeProfile>
</activeProfiles>
</settings>
----
-After you configure this, all the maven objects will be available to your
builds.
-
-== Using the examples
-
-The examples will create servers and use most of the maven components as real
application were supposed to do.
-You can do this by running these examples after the `.m2` profile
installations for the staged repository.
-
-Of course, you can use your own applications after you have staged the maven
repository.
+After you configure this, the maven artifacts for the release candidate will
be available to your builds.
diff --git a/docs/user-manual/configuring-transports.adoc
b/docs/user-manual/configuring-transports.adoc
index 9a364be724..6a68e7ebbb 100644
--- a/docs/user-manual/configuring-transports.adoc
+++ b/docs/user-manual/configuring-transports.adoc
@@ -303,8 +303,8 @@ When used on an `acceptor` this is the path to the SSL key
store on the server w
When used on a `connector` this is the path to the client-side SSL key store
which holds the client certificates.
This is only relevant for a `connector` if you are using 2-way SSL (i.e.
mutual authentication).
Although this value is configured on the server, it is downloaded and used by
the client.
-If the client needs to use a different path from that set on the server then
it can override the server-side setting by either using the customary
"javax.net.ssl.keyStore" system property or the ActiveMQ-specific
"org.apache.activemq.ssl.keyStore" system property.
-The ActiveMQ-specific system property is useful if another component on the
client is already making use of the standard Java system property.
+If the client needs to use a different path from that set on the server then
it can override the server-side setting by either using the customary
"javax.net.ssl.keyStore" system property or the Artemis-specific
"org.apache.activemq.ssl.keyStore" system property.
+The Artemis-specific system property is useful if another component on the
client is already making use of the standard Java system property.
keyStorePassword::
When used on an `acceptor` this is the password for the server-side keystore.
@@ -312,21 +312,21 @@ When used on an `acceptor` this is the password for the
server-side keystore.
When used on a `connector` this is the password for the client-side keystore.
This is only relevant for a `connector` if you are using 2-way SSL (i.e.
mutual authentication).
Although this value can be configured on the server, it is downloaded and used
by the client.
-If the client needs to use a different password from that set on the server
then it can override the server-side setting by either using the customary
"javax.net.ssl.keyStorePassword" system property or the ActiveMQ-specific
"org.apache.activemq.ssl.keyStorePassword" system property.
-The ActiveMQ-specific system property is useful if another component on the
client is already making use of the standard Java system property.
+If the client needs to use a different password from that set on the server
then it can override the server-side setting by either using the customary
"javax.net.ssl.keyStorePassword" system property or the Artemis-specific
"org.apache.activemq.ssl.keyStorePassword" system property.
+The Artemis-specific system property is useful if another component on the
client is already making use of the standard Java system property.
keyStoreType::
The type of keystore being used.
For example, `JKS`, `JCEKS`, `PKCS12`, `PEM` etc.
-This value can also be set via the "javax.net.ssl.keyStoreType" system
property or the ActiveMQ-specific "org.apache.activemq.ssl.keyStoreType" system
property.
-The ActiveMQ-specific system property is useful if another component on the
client is already making use of the standard Java system property.
+This value can also be set via the "javax.net.ssl.keyStoreType" system
property or the Artemis-specific "org.apache.activemq.ssl.keyStoreType" system
property.
+The Artemis-specific system property is useful if another component on the
client is already making use of the standard Java system property.
Default is `JKS`.
keyStoreProvider::
The provider used for the keystore.
For example, `SUN`, `SunJCE`, etc.
-This value can also be set via the "javax.net.ssl.keyStoreProvider" system
property or the ActiveMQ-specific "org.apache.activemq.ssl.keyStoreProvider"
system property.
-The ActiveMQ-specific system property is useful if another component on the
client is already making use of the standard Java system property.
+This value can also be set via the "javax.net.ssl.keyStoreProvider" system
property or the Artemis-specific "org.apache.activemq.ssl.keyStoreProvider"
system property.
+The Artemis-specific system property is useful if another component on the
client is already making use of the standard Java system property.
Default is `null`.
keyStoreAlias::
@@ -343,8 +343,8 @@ This is only relevant for an `acceptor` if you are using
2-way SSL (i.e. mutual
+
When used on a `connector` this is the path to the client-side SSL key store
which holds the public keys of all the servers that the client trusts.
Although this value can be configured on the server, it is downloaded and used
by the client.
-If the client needs to use a different path from that set on the server then
it can override the server-side setting by either using the customary
"javax.net.ssl.trustStore" system property or the ActiveMQ-specific
"org.apache.activemq.ssl.trustStore" system property.
-The ActiveMQ-specific system property is useful if another component on the
client is already making use of the standard Java system property.
+If the client needs to use a different path from that set on the server then
it can override the server-side setting by either using the customary
"javax.net.ssl.trustStore" system property or the Artemis-specific
"org.apache.activemq.ssl.trustStore" system property.
+The Artemis-specific system property is useful if another component on the
client is already making use of the standard Java system property.
trustStorePassword::
When used on an `acceptor` this is the password for the server-side trust
store.
@@ -352,21 +352,21 @@ This is only relevant for an `acceptor` if you are using
2-way SSL (i.e. mutual
+
When used on a `connector` this is the password for the client-side truststore.
Although this value can be configured on the server, it is downloaded and used
by the client.
-If the client needs to use a different password from that set on the server
then it can override the server-side setting by either using the customary
"javax.net.ssl.trustStorePassword" system property or the ActiveMQ-specific
"org.apache.activemq.ssl.trustStorePassword" system property.
-The ActiveMQ-specific system property is useful if another component on the
client is already making use of the standard Java system property.
+If the client needs to use a different password from that set on the server
then it can override the server-side setting by either using the customary
"javax.net.ssl.trustStorePassword" system property or the Artemis-specific
"org.apache.activemq.ssl.trustStorePassword" system property.
+The Artemis-specific system property is useful if another component on the
client is already making use of the standard Java system property.
trustStoreType::
The type of truststore being used.
For example, `JKS`, `JCEKS`, `PKCS12`, `PEM` etc.
-This value can also be set via the "javax.net.ssl.trustStoreType" system
property or the ActiveMQ-specific "org.apache.activemq.ssl.trustStoreType"
system property.
-The ActiveMQ-specific system property is useful if another component on the
client is already making use of the standard Java system property.
+This value can also be set via the "javax.net.ssl.trustStoreType" system
property or the Artemis-specific "org.apache.activemq.ssl.trustStoreType"
system property.
+The Artemis-specific system property is useful if another component on the
client is already making use of the standard Java system property.
Default is `JKS`.
trustStoreProvider::
The provider used for the truststore.
For example, `SUN`, `SunJCE`, etc.
-This value can also be set via the "javax.net.ssl.trustStoreProvider" system
property or the ActiveMQ-specific "org.apache.activemq.ssl.trustStoreProvider"
system property.
-The ActiveMQ-specific system property is useful if another component on the
client is already making use of the standard Java system property.
+This value can also be set via the "javax.net.ssl.trustStoreProvider" system
property or the Artemis-specific "org.apache.activemq.ssl.trustStoreProvider"
system property.
+The Artemis-specific system property is useful if another component on the
client is already making use of the standard Java system property.
Default is `null`.
enabledCipherSuites::
@@ -412,7 +412,7 @@ Valid values are `true` or `false`.
Default is `false`.
forceSSLParameters::
-When used on a `connector` any SSL settings that are set as parameters on the
connector will be used instead of JVM system properties including both
javax.net.ssl and ActiveMQ system properties to configure the SSL context for
this connector.
+When used on a `connector` any SSL settings that are set as parameters on the
connector will be used instead of JVM system properties including both
javax.net.ssl and Artemis system properties to configure the SSL context for
this connector.
+
Valid values are `true` or `false`.
Default is `false`.
diff --git a/docs/user-manual/docker.adoc b/docs/user-manual/docker.adoc
index b80295ae33..14865f9a87 100644
--- a/docs/user-manual/docker.adoc
+++ b/docs/user-manual/docker.adoc
@@ -49,7 +49,7 @@ In order to build an image you need a binary distribution.
This can be sourced *locally* (in which case you need to build the project
first) or *remotely* based on an official Apache release.
=== Using a Local Release
-If you want to use a local binary distribution then build it from the root of
the ActiveMQ source tree, e.g.:
+If you want to use a local binary distribution then build it from the root of
the Artemis source tree, e.g.:
[,console]
----
$ mvn -Prelease package -DskipTests
diff --git a/docs/user-manual/examples.adoc b/docs/user-manual/examples.adoc
index 81973b34d3..26130fb3f7 100644
--- a/docs/user-manual/examples.adoc
+++ b/docs/user-manual/examples.adoc
@@ -25,28 +25,6 @@ First, run `mvn clean package` in the repository root to
prepare a broker distri
To run any example, simply `cd` into the appropriate example directory and
type `mvn verify` or `mvn install` (For details please read the readme.md in
each example directory).
-You can use the profile `-Pexamples` to run multiple examples under any
example tree.
-
-For each example, you will have a created server under `./target/server0`
(some examples use more than one server).
-
-You have the option to prevent the example from starting the server (e.g. if
you want to start the server manually) by simply specifying the `-PnoServer`
profile, e.g.:
-
-[,sh]
-----
-# running an example without running the server
-mvn verify -PnoServer
-----
-
-Also under `./target` there will be a script repeating the commands to create
each server.
-Here is the `create-server0.sh` generated by the `Queue` example.
-This is useful to see exactly what command(s) are required to configure the
server(s).
-
-[,sh]
-----
-# These are the commands used to create server0
-/myInstallDirectory/apache-artemis/bin/artemis create --allow-anonymous
--silent --force --no-web --user guest --password guest --role guest
--port-offset 0 --data ./data --allow-anonymous --no-autotune --verbose
/myInstallDirectory/apache-artemis-1.1.0/examples/features/standard/queue/target/server0
-----
-
Several examples use UDP clustering which may not work in your environment by
default.
On linux the command would be:
@@ -71,101 +49,120 @@ On this case taken from the `Queue` example:
[,sh]
----
-[INFO] -------------< org.apache.activemq.examples.broker:queue >--------------
-[INFO] Building ActiveMQ Artemis JMS Queue Example 2.32.0
+[INFO] --------------< org.apache.artemis.examples.broker:queue >--------------
+[INFO] Building Apache Artemis JMS Queue Example 2.50.0
[INFO] from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
-[INFO] --- enforcer:3.3.0:enforce (enforce-maven-version) @ queue ---
+[INFO] --- clean:3.5.0:clean (default-clean) @ queue ---
+[INFO] Deleting
/home/user/artemis-examples/examples/features/standard/queue/target
+[INFO]
+[INFO] --- enforcer:3.5.0:enforce (enforce-maven-version) @ queue ---
[INFO] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion
passed
[INFO]
-[INFO] --- enforcer:3.3.0:enforce (enforce-java-version) @ queue ---
+[INFO] --- enforcer:3.5.0:enforce (enforce-java-version) @ queue ---
[INFO] Rule 0: org.apache.maven.enforcer.rules.version.RequireJavaVersion
passed
[INFO]
-[INFO] --- remote-resources:3.1.0:process (process-resource-bundles) @ queue
---
-[INFO] Preparing remote bundle
org.apache.apache.resources:apache-jar-resource-bundle:1.5
+[INFO] --- remote-resources:3.3.0:process (process-resource-bundles) @ queue
---
+[INFO] Preparing remote bundle
org.apache.apache.resources:apache-jar-resource-bundle:1.7
[INFO] Copying 3 resources from 1 bundle.
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ queue ---
[INFO] Copying 1 resource from src/main/resources to target/classes
[INFO] Copying 3 resources from target/maven-shared-archive-resources to
target/classes
[INFO]
-[INFO] --- compiler:3.11.0:compile (default-compile) @ queue ---
-[INFO] Changes detected - recompiling the module! :source
-[INFO] Compiling 1 source file with javac [debug target 11] to target/classes
+[INFO] --- compiler:3.14.0:compile (default-compile) @ queue ---
+[INFO] Recompiling the module because of changed source code.
+[INFO] Compiling 1 source file with javac [debug release 17] to target/classes
[INFO]
[INFO] --- resources:3.3.1:testResources (default-testResources) @ queue ---
-[INFO] skip non existing resourceDirectory
/home/user/activemq-artemis-examples/examples/features/standard/queue/src/test/resources
+[INFO] skip non existing resourceDirectory
/home/user/artemis-examples/examples/features/standard/queue/src/test/resources
[INFO] Copying 3 resources from target/maven-shared-archive-resources to
target/test-classes
[INFO]
-[INFO] --- compiler:3.11.0:testCompile (default-testCompile) @ queue ---
+[INFO] --- compiler:3.14.0:testCompile (default-testCompile) @ queue ---
[INFO] No sources to compile
[INFO]
-[INFO] --- surefire:2.22.2:test (default-test) @ queue ---
-[INFO]
-[INFO] --- jar:3.3.0:jar (default-jar) @ queue ---
-[INFO] Building jar:
/home/user/activemq-artemis-examples/examples/features/standard/queue/target/queue-2.32.0.jar
+[INFO] --- surefire:3.5.3:test (default-test) @ queue ---
[INFO]
-[INFO] --- site:3.12.1:attach-descriptor (attach-descriptor) @ queue ---
-[INFO] Skipping because packaging 'jar' is not pom.
+[INFO] --- jar:3.4.2:jar (default-jar) @ queue ---
+[INFO] Building jar:
/home/user/artemis-examples/examples/features/standard/queue/target/queue-2.50.0.jar
[INFO]
-[INFO] --- source:3.3.0:jar-no-fork (attach-sources) @ queue ---
-[INFO] Building jar:
/home/user/activemq-artemis-examples/examples/features/standard/queue/target/queue-2.32.0-sources.jar
+[INFO] --- artemis:2.50.0:create (create) @ queue ---
[INFO]
-[INFO] --- artemis:2.32.0:create (create) @ queue ---
-[INFO]
-[INFO] --- artemis:2.32.0:cli (start) @ queue ---
+[INFO] --- artemis:2.50.0:cli (start) @ queue ---
[INFO] awaiting server to start
server-out: _ _ _
server-out: / \ ____| |_ ___ __ __(_) _____
server-out: / _ \| _ \ __|/ _ \ \/ | |/ __/
server-out: / ___ \ | \/ |_/ __/ |\/| | |\___ \
server-out: /_/ \_\| \__\____|_| |_|_|/___ /
-server-out: Apache ActiveMQ Artemis 2.32.0
+server-out: Apache Artemis 2.50.0
server-out:
server-out:
[INFO] awaiting server to start
-server-out:2023-12-14 14:33:06,314 INFO
[org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting
ActiveMQ Artemis Server version 2.32.0
-server-out:2023-12-14 14:33:06,339 INFO
[org.apache.activemq.artemis.core.server] AMQ221000: primary Message Broker is
starting with configuration Broker Configuration
(clustered=false,journalDirectory=./data/journal,bindingsDirectory=./data/bindings,largeMessagesDirectory=./data/large-messages,pagingDirectory=./data/paging)
-server-out:2023-12-14 14:33:06,354 INFO
[org.apache.activemq.artemis.core.server] AMQ221012: Using AIO Journal
-server-out:2023-12-14 14:33:06,380 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
-server-out:2023-12-14 14:33:06,391 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-server]. Adding protocol support for: CORE
-server-out:2023-12-14 14:33:06,391 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-amqp-protocol]. Adding protocol support for: AMQP
-server-out:2023-12-14 14:33:06,391 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
-server-out:2023-12-14 14:33:06,392 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-mqtt-protocol]. Adding protocol support for: MQTT
-server-out:2023-12-14 14:33:06,392 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-openwire-protocol]. Adding protocol support for: OPENWIRE
-server-out:2023-12-14 14:33:06,392 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-stomp-protocol]. Adding protocol support for: STOMP
-server-out:2023-12-14 14:33:06,411 INFO
[org.apache.activemq.artemis.core.server] AMQ221034: Waiting indefinitely to
obtain primary lock
-server-out:2023-12-14 14:33:06,411 INFO
[org.apache.activemq.artemis.core.server] AMQ221035: Primary Server Obtained
primary lock
-server-out:2023-12-14 14:33:06,450 INFO
[org.apache.activemq.artemis.core.server] AMQ221080: Deploying address DLQ
supporting [ANYCAST]
-server-out:2023-12-14 14:33:06,454 INFO
[org.apache.activemq.artemis.core.server] AMQ221003: Deploying ANYCAST queue
DLQ on address DLQ
-server-out:2023-12-14 14:33:06,476 INFO
[org.apache.activemq.artemis.core.server] AMQ221080: Deploying address
ExpiryQueue supporting [ANYCAST]
-server-out:2023-12-14 14:33:06,476 INFO
[org.apache.activemq.artemis.core.server] AMQ221003: Deploying ANYCAST queue
ExpiryQueue on address ExpiryQueue
-server-out:2023-12-14 14:33:06,681 INFO
[org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at
0.0.0.0:61616 for protocols [CORE,MQTT,AMQP,STOMP,HORNETQ,OPENWIRE]
-server-out:2023-12-14 14:33:06,683 INFO
[org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at
0.0.0.0:5445 for protocols [HORNETQ,STOMP]
-server-out:2023-12-14 14:33:06,685 INFO
[org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at
0.0.0.0:5672 for protocols [AMQP]
-server-out:2023-12-14 14:33:06,687 INFO
[org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at
0.0.0.0:1883 for protocols [MQTT]
-server-out:2023-12-14 14:33:06,689 INFO
[org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at
0.0.0.0:61613 for protocols [STOMP]
-server-out:2023-12-14 14:33:06,690 INFO
[org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
-server-out:2023-12-14 14:33:06,690 INFO
[org.apache.activemq.artemis.core.server] AMQ221001: Apache ActiveMQ Artemis
Message Broker version 2.32.0 [0.0.0.0,
nodeID=b20d82dd-9a8d-11ee-a56d-000c2997e711]
+server-out:2025-12-23 11:07:42,914 INFO
[org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting Apache
Artemis Server version 2.50.0
+server-out:2025-12-23 11:07:42,943 INFO
[org.apache.activemq.artemis.core.server] AMQ221000: Primary message broker is
starting with configuration Broker Configuration
(clustered=false,journalDirectory=./data/journal,bindingsDirectory=./data/bindings,largeMessagesDirectory=./data/large-messages,pagingDirectory=./data/paging)
+server-out:2025-12-23 11:07:42,961 INFO
[org.apache.activemq.artemis.core.server] AMQ221012: Using AIO Journal
+server-out:2025-12-23 11:07:42,989 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
+server-out:2025-12-23 11:07:43,000 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-server]. Adding protocol support for: CORE
+server-out:2025-12-23 11:07:43,001 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-amqp-protocol]. Adding protocol support for: AMQP
+server-out:2025-12-23 11:07:43,001 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
+server-out:2025-12-23 11:07:43,001 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-mqtt-protocol]. Adding protocol support for: MQTT
+server-out:2025-12-23 11:07:43,001 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-openwire-protocol]. Adding protocol support for: OPENWIRE
+server-out:2025-12-23 11:07:43,002 INFO
[org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found:
[artemis-stomp-protocol]. Adding protocol support for: STOMP
+server-out:2025-12-23 11:07:43,020 INFO
[org.apache.activemq.artemis.core.server] AMQ221034: Waiting indefinitely to
obtain primary lock
+server-out:2025-12-23 11:07:43,020 INFO
[org.apache.activemq.artemis.core.server] AMQ221035: Primary Server Obtained
primary lock
+server-out:2025-12-23 11:07:43,068 INFO
[org.apache.activemq.artemis.core.server] AMQ221080: Deploying address DLQ
supporting [ANYCAST]
+server-out:2025-12-23 11:07:43,076 INFO
[org.apache.activemq.artemis.core.server] AMQ221003: Deploying ANYCAST queue
DLQ on address DLQ
+server-out:2025-12-23 11:07:43,100 INFO
[org.apache.activemq.artemis.core.server] AMQ221080: Deploying address
ExpiryQueue supporting [ANYCAST]
+server-out:2025-12-23 11:07:43,101 INFO
[org.apache.activemq.artemis.core.server] AMQ221003: Deploying ANYCAST queue
ExpiryQueue on address ExpiryQueue
+server-out:2025-12-23 11:07:43,316 INFO
[org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at
0.0.0.0:61616 for protocols [CORE,MQTT,AMQP,STOMP,HORNETQ,OPENWIRE]
+server-out:2025-12-23 11:07:43,318 INFO
[org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at
0.0.0.0:5445 for protocols [HORNETQ,STOMP]
+server-out:2025-12-23 11:07:43,320 INFO
[org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at
0.0.0.0:5672 for protocols [AMQP]
+server-out:2025-12-23 11:07:43,321 INFO
[org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at
0.0.0.0:1883 for protocols [MQTT]
+server-out:2025-12-23 11:07:43,323 INFO
[org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at
0.0.0.0:61613 for protocols [STOMP]
+server-out:2025-12-23 11:07:43,324 INFO
[org.apache.activemq.artemis.core.server] AMQ221007: Server is now active
+server-out:2025-12-23 11:07:43,324 INFO
[org.apache.activemq.artemis.core.server] AMQ221001: Apache Artemis Message
Broker version 2.50.0 [0.0.0.0, nodeID=9a6b5ad2-dfef-11f0-ad3c-000c2997e711]
[INFO] Server started
[INFO]
-[INFO] --- artemis:2.32.0:runClient (runClient) @ queue ---
+[INFO] --- artemis:2.50.0:runClient (runClient) @ queue ---
Sent message: This is a text message
Received message: This is a text message
[INFO]
-[INFO] --- artemis:2.32.0:stop (stop) @ queue ---
-server-out:2023-12-14 14:33:08,295 INFO
[org.apache.activemq.artemis.core.server] AMQ221002: Apache ActiveMQ Artemis
Message Broker version 2.32.0 [b20d82dd-9a8d-11ee-a56d-000c2997e711] stopped,
uptime 1.969 seconds
+[INFO] --- artemis:2.50.0:stop (stop) @ queue ---
+server-out:2025-12-23 11:07:44,856 INFO
[org.apache.activemq.artemis.core.server] AMQ221002: Apache Artemis Message
Broker version 2.50.0 [9a6b5ad2-dfef-11f0-ad3c-000c2997e711] stopped, uptime
1.929 seconds
server-out:Server stopped!
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
-[INFO] Total time: 4.845 s
-[INFO] Finished at: 2023-12-14T14:33:08Z
+[INFO] Total time: 4.642 s
+[INFO] Finished at: 2025-12-23T11:07:45Z
[INFO] ------------------------------------------------------------------------
----
-This list includes a preview of some examples in the
https://github.com/apache/artemis-examples[Examples Repository^].
+You can use the profile `-Pexamples` to run multiple examples under any
example tree.
+
+For each example, you will have a created server under `./target/server0`
(some examples use more than one server).
+
+You have the option to prevent the example from starting the server (e.g. if
you want to start the server manually) by simply specifying the `-PnoServer`
profile, e.g.:
+
+[,sh]
+----
+# running an example without running the server
+mvn verify -PnoServer
+----
+
+Also under `./target` there will be a script repeating the commands to create
each server.
+Here is the `create-server0.sh` generated by the `Queue` example.
+This is useful to see exactly what command(s) are required to configure the
server(s).
+
+[,sh]
+----
+# These are the commands used to create server0
+/myInstallDirectory/apache-artemis/bin/artemis create --allow-anonymous
--silent --force --no-web --user guest --password guest --role guest
--port-offset 0 --data ./data --allow-anonymous --no-autotune --verbose
/myInstallDirectory/apache-artemis-1.1.0/examples/features/standard/queue/target/server0
+----
+
+The below list includes a preview of some examples in the
https://github.com/apache/artemis-examples[Examples Repository^].
See the repository for more.
== Application-Layer Failover
@@ -317,7 +314,7 @@ These "expired" messages can later be consumed from the
expiry address for furth
== Resource Adapter example
-This examples shows how to build the activemq resource adapters a rar for
deployment in other Application Server's
+This examples shows how to build the Artemis resource adapters a rar for
deployment in other Application Server's
== HTTP Transport
diff --git a/docs/user-manual/ha.adoc b/docs/user-manual/ha.adoc
index 50bd92d699..ca3d37b8cd 100644
--- a/docs/user-manual/ha.adoc
+++ b/docs/user-manual/ha.adoc
@@ -745,7 +745,7 @@ This is configured via the `ha-policy` element in the
`broker.xml` file like so:
the above example is configured to use replication, in this case the `primary`
and `backup` configurations must match those for normal replication as in the
previous chapter.
`shared-store` is also supported
-image::images/ha-colocated.png[ActiveMQ Artemis ha-colocated.png]
+image::images/ha-colocated.png[Artemis ha-colocated.png]
=== Configuring Connectors and Acceptors
@@ -810,7 +810,7 @@ The caveat here is if you configure a backup to scale down.
Another disadvantage is that it is possible to lose message ordering.
This happens in the following scenario, say you have 2 active servers and
messages are distributed evenly between the servers from a single producer, if
one of the servers scales down then the messages sent back to the other server
will be in the queue after the ones already there, so server 1 could have
messages 1,3,5,7,9 and server 2 would have 2,4,6,8,10, if server 2 scales down
the order in server 1 would be 1,3,5,7,9,2,4,6,8,10.
-image::images/ha-scaledown.png[ActiveMQ Artemis ha-scaledown.png]
+image::images/ha-scaledown.png[Artemis ha-scaledown.png]
The configuration for an active server to scale down would be something like:
diff --git a/docs/user-manual/karaf.adoc b/docs/user-manual/karaf.adoc
index 8d3c143760..28ef6ea9ba 100644
--- a/docs/user-manual/karaf.adoc
+++ b/docs/user-manual/karaf.adoc
@@ -19,13 +19,13 @@ This will add broker-related features
----
karaf@root()> feature:list | grep artemis
-artemis | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | Full ActiveMQ Artemis broker with default
configuration
+artemis | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | Full Apache Artemis broker with default configuration
netty-core | 4.0.32.Final | | Uninstalled |
artemis-1.3.0-SNAPSHOT | Netty libraries
-artemis-core | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | ActiveMQ Artemis broker libraries
-artemis-amqp | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | ActiveMQ Artemis AMQP protocol libraries
-artemis-stomp | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | ActiveMQ Artemis Stomp protocol libraries
-artemis-mqtt | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | ActiveMQ Artemis MQTT protocol libraries
-artemis-hornetq | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | ActiveMQ Artemis HornetQ protocol libraries
+artemis-core | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | Apache Artemis broker libraries
+artemis-amqp | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | Apache Artemis AMQP protocol libraries
+artemis-stomp | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | Apache Artemis Stomp protocol libraries
+artemis-mqtt | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | Apache Artemis MQTT protocol libraries
+artemis-hornetq | 1.3.0.SNAPSHOT | | Uninstalled |
artemis-1.3.0-SNAPSHOT | Apache Artemis HornetQ protocol libraries
----
Feature named `artemis` contains full broker installation, so running
diff --git a/docs/user-manual/management-console.adoc
b/docs/user-manual/management-console.adoc
index 222d8813dd..22a59fb5db 100644
--- a/docs/user-manual/management-console.adoc
+++ b/docs/user-manual/management-console.adoc
@@ -14,7 +14,7 @@ To access the management console, use a browser and go to the
URL link:[http://l
A login screen will be presented, if your broker is secure, you will need to
use a user with admin role, if it is unsecure simply enter any user/password.
-image::images/console-login.png[ActiveMQ Artemis Console Login]
+image::images/console-login.png[Apache Artemis Console Login]
== Security
@@ -47,7 +47,7 @@ Problems with Jolokia security are often observed as the
ability to login to the
Once logged in you should be presented with a screen similar to.
-image::images/console-artemis-plugin.png[ActiveMQ Artemis Console Artemis
Plugin]
+image::images/console-artemis-plugin.png[Apache Artemis Console Artemis Plugin]
=== Navigation Menu
diff --git a/docs/user-manual/management.adoc b/docs/user-manual/management.adoc
index 2d390a4b00..111bba26f9 100644
--- a/docs/user-manual/management.adoc
+++ b/docs/user-manual/management.adoc
@@ -11,7 +11,7 @@ There are numerous ways to access the management API:
* Using JMX -- _JMX_ is the standard way to manage Java applications
* Using Jolokia -- Jolokia exposes the JMX API of an application through an
_HTTP interface_
* Using the Core Client -- management operations are sent to the broker using
_Core Client messages_
-* Using any JMS Client -- management operations are sent to Apache ActiveMQ
Artemis server using _JMS Client messages_
+* Using any JMS Client -- management operations are sent to Apache Artemis
server using _JMS Client messages_
* Web Console -- a web application which provides a graphical interface to the
management API.
Although there are four different ways to manage the broker, each API supports
the same functionality.
@@ -525,7 +525,7 @@ To manage several brokers from the _same_ MBeanServer, the
JMX domain can be con
[,xml]
----
-<!-- use a specific JMX domain for ActiveMQ Artemis MBeans -->
+<!-- use a specific JMX domain for Apache Artemis MBeans -->
<jmx-domain>my.org.apache.activemq</jmx-domain>
----
diff --git a/docs/user-manual/message-grouping.adoc
b/docs/user-manual/message-grouping.adoc
index 0ad8b0268f..2fb27da377 100644
--- a/docs/user-manual/message-grouping.adoc
+++ b/docs/user-manual/message-grouping.adoc
@@ -89,7 +89,7 @@ This closes the message group so if another message is sent
in the future with t
== Notifying Consumer of Group Ownership change
-ActiveMQ supports putting a boolean header on the first message sent to a
consumer for a particular message group.
+Artemis supports putting a boolean header on the first message sent to a
consumer for a particular message group.
To enable this you must set a header key that the broker will use to set the
flag.
diff --git a/docs/user-manual/network-isolation.adoc
b/docs/user-manual/network-isolation.adoc
index 0731864f84..68ced2f679 100644
--- a/docs/user-manual/network-isolation.adoc
+++ b/docs/user-manual/network-isolation.adoc
@@ -122,7 +122,7 @@ Once you lose connectivity towards `10.0.0.1` on the given
example the broker wi
----
09:49:24,562 WARN
[org.apache.activemq.artemis.core.server.NetworkHealthCheck] Ping Address
/10.0.0.1 wasn't reacheable
09:49:36,577 INFO
[org.apache.activemq.artemis.core.server.NetworkHealthCheck] Network is
unhealthy, stopping service
ActiveMQServerImpl::serverUUID=04fd5dd8-b18c-11e6-9efe-6a0001921ad0
-09:49:36,625 INFO [org.apache.activemq.artemis.core.server] AMQ221002: Apache
ActiveMQ Artemis Message Broker version 1.6.0
[04fd5dd8-b18c-11e6-9efe-6a0001921ad0] stopped, uptime 14.787 seconds
+09:49:36,625 INFO [org.apache.activemq.artemis.core.server] AMQ221002: Apache
Artemis Message Broker version 1.6.0 [04fd5dd8-b18c-11e6-9efe-6a0001921ad0]
stopped, uptime 14.787 seconds
09:50:00,653 WARN
[org.apache.activemq.artemis.core.server.NetworkHealthCheck] ping: sendto: No
route to host
09:50:10,656 WARN
[org.apache.activemq.artemis.core.server.NetworkHealthCheck] Host is down:
java.net.ConnectException: Host is down
at java.net.Inet6AddressImpl.isReachable0(Native Method)
[rt.jar:1.8.0_73]
@@ -162,7 +162,7 @@ Once you reestablish your network connections towards the
configured check-list:
09:53:23,555 INFO [org.apache.activemq.artemis.core.server] AMQ221020:
Started Acceptor at 0.0.0.0:1883 for protocols [MQTT]
09:53:23,556 INFO [org.apache.activemq.artemis.core.server] AMQ221020:
Started Acceptor at 0.0.0.0:61613 for protocols [STOMP]
09:53:23,556 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server
is now active
-09:53:23,556 INFO [org.apache.activemq.artemis.core.server] AMQ221001: Apache
ActiveMQ Artemis Message Broker version 1.6.0 [0.0.0.0,
nodeID=04fd5dd8-b18c-11e6-9efe-6a0001921ad0]
+09:53:23,556 INFO [org.apache.activemq.artemis.core.server] AMQ221001: Apache
Artemis Message Broker version 1.6.0 [0.0.0.0,
nodeID=04fd5dd8-b18c-11e6-9efe-6a0001921ad0]
----
[IMPORTANT]
diff --git a/docs/user-manual/upgrading.adoc b/docs/user-manual/upgrading.adoc
index 47ab07afd9..52adf557a9 100644
--- a/docs/user-manual/upgrading.adoc
+++ b/docs/user-manual/upgrading.adoc
@@ -3,8 +3,7 @@
:idseparator: -
:docinfo: shared
-Apache ActiveMQ is runnable out of the box by executing the command:
`./bin/activemq run`.
-The {project-name-short} broker follows a different paradigm where the project
distribution serves as the broker "home" and one or more broker "instances" are
created which reference the "home" for resources (e.g. jar files) which can be
safely shared between broker instances.
+The {project-name-short} broker follows a paradigm where the project
distribution serves as the broker "home" and then one or more broker
"instances" are created which reference the "home" for resources (e.g. jar
files) which can be safely shared between broker instances.
Therefore, an instance of the broker must be created before it can be run.
This may seem like an overhead at first glance, but it becomes very practical
when updating to a new version, for example.
diff --git a/docs/user-manual/using-cli.adoc b/docs/user-manual/using-cli.adoc
index bc10c57388..1d74635abf 100644
--- a/docs/user-manual/using-cli.adoc
+++ b/docs/user-manual/using-cli.adoc
@@ -26,7 +26,7 @@ You can get a complete list of available commands by typing:
----
$ ./artemis help
Usage: artemis [COMMAND]
-ActiveMQ Artemis Command Line
+Apache Artemis Command Line
Commands:
help use 'help <command>' for more information
pwd Information on current folder and instance.
@@ -149,7 +149,7 @@ Create a new broker instance.
--cluster-user=<clusterUser>
The user to use for clustering. Default: input.
--clustered Enable clustering.
- --data=<data> Directory where ActiveMQ data are stored. Paths
+ --data=<data> Directory where Apache Artemis data is stored.
Paths
can be absolute or relative to artemis.instance
directory. Default: data.
--default-port=<defaultPort>
@@ -158,7 +158,7 @@ Create a new broker instance.
--disable-persistence Disable message persistence to the journal
--encoding=<encoding> The encoding that text files should use. Default:
UTF-8.
- --etc=<etc> Directory where ActiveMQ configuration is located.
+ --etc=<etc> Directory where Apache Artemis configuration is
located.
Paths can be absolute or relative to artemis.
instance directory. Default: etc.
--failover-on-shutdown Whether broker shutdown will trigger failover for
@@ -172,7 +172,7 @@ Create a new broker instance.
--global-max-size=<globalMaxSize>
Maximum amount of memory which message data may
consume. Default: half of the JVM's max memory.
- --home=<home> Directory where ActiveMQ Artemis is installed.
+ --home=<home> Directory where Apache Artemis is installed.
--host=<host> Broker's host name. Default: 0.0.0.0 or input if
clustered).
--http-host=<httpHost> Embedded web server's host name. Default:
@@ -357,12 +357,12 @@ The shell provides an interface that can be used to
execute commands directly wi
/ _ \| _ \ __|/ _ \ \/ | |/ __/
/ ___ \ | \/ |_/ __/ |\/| | |\___ \
/_/ \_\| \__\____|_| |_|_|/___ /
- Apache ActiveMQ Artemis
+ Apache Artemis
For a list of commands, type help or press <TAB>:
Type exit or press <CTRL-D> to leave the session:
-Apache ActiveMQ Artemis >
+Apache Artemis >
----
=== Connecting Interactively
@@ -371,7 +371,7 @@ It is possible to authenticate your CLI client once to the
server and reuse the
[,console]
----
-Apache ActiveMQ Artemis > connect --user=myUser --password=myPass --url
tcp://localhost:61616
+Apache Artemis > connect --user=myUser --password=myPass --url
tcp://localhost:61616
Connection brokerURL = tcp://localhost:61616
Connection Successful!
----
@@ -381,7 +381,7 @@ For example the sub-command `queue stat` will reuse
previous information to perf
[%nowrap,console]
----
-Apache ActiveMQ Artemis > queue stat
+Apache Artemis > queue stat
Connection brokerURL = tcp://localhost:61616
|NAME |ADDRESS
|CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED_COUNT|ROUTING_TYPE|
|DLQ |DLQ |0 |0
|0 |0 |0 |0 |ANYCAST |
@@ -407,7 +407,7 @@ $ ./artemis shell --user myUser --password myPass
...
-Apache ActiveMQ Artemis > queue stat
+Apache Artemis > queue stat
Connection brokerURL = tcp://localhost:61616
|NAME |ADDRESS
|CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED_COUNT|ROUTING_TYPE|
|DLQ |DLQ |0 |0
|0 |0 |0 |0 |ANYCAST |
diff --git a/docs/user-manual/versions.adoc b/docs/user-manual/versions.adoc
index 661d5afde6..3cfcde0d65 100644
--- a/docs/user-manual/versions.adoc
+++ b/docs/user-manual/versions.adoc
@@ -15,11 +15,11 @@ NOTE: Follow the general upgrade procedure outlined in the
xref:upgrading.adoc#u
== 2.50.0
-https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=xxx[Full
release notes]
+https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=12356368[Full
release notes]
=== Highlights
-* ...
+* First release as Apache Artemis!
=== Upgrading from 2.44.0
@@ -53,7 +53,7 @@ More details available xref:proxy-protocol.adoc[here].
=== Upgrading from 2.42.0
-* As part of the work for
https://issues.apache.org/jira/browse/ARTEMIS-5557[ARTEMIS-5557] to report
executor service metrics the names of many ActiveMQ-related threads were
changed to be more clear and consistent.
+* As part of the work for
https://issues.apache.org/jira/browse/ARTEMIS-5557[ARTEMIS-5557] to report
executor service metrics the names of many Artemis-related threads were changed
to be more clear and consistent.
This will be visible, for example, when inspecting thread dumps or if you
happen to include the thread name in your logging output.
Here's examples of old names vs. the new ones.
+
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
