Hi Calle-
Thanks for the quick turn-around on the test-and-report-back.
We are preparing a v6.0.1 that will have the fix and should be out in a week or
so.
As far as the other issue, that log message is from a JBoss class about a JBoss
module. Please start with the jboss community and if they
Hi,
Many unexpected things occured today but I managed to perform a very quick test.
I replaced the ra.xml only since I use a remote broker. I deployed the modified
activemq-rar.rar on a Wildfly 29 without any problems. I also deployed a MDB
which was able to consume a message from a queue on
Found the problem with spring boot dependency management, thanks for the help
and sorry for the off topic problem !
-Message d'origine-
De : Robbie Gemmell
Envoyé : mercredi 22 novembre 2023 12:19
À : users@activemq.apache.org
Objet : Re: [ActiveMQ Classic] Broker dependencies in 5.18.3
Something about your specific build is making Maven select 5.18.2 for
those modules, as the 5.18.3 broker module does originally depend on
the 5.18.3 modules.
Maven will resolve all the [transitive] dependencies of your build,
and pick one version for everything used. In that process, something
Hello Team,
I'm using ActiveMQ broker on multiple projects, and we just made the update
from 5.18.2 to 5.18.3 to correct CVE-202346604.
In my maven dependencies, I just declare activemq-broker and let him handle his
dependencies.
However, he seems to download his ActiveMQ dependencies
Hello Team,
we are running two nodes with artemis 2.30 brokers connected with a static
network connector.
CORE and OPENWIRE are enabled on the same client acceptor.
>From remote there is a java client connecting with a failover transport,
doing a periodic send while broker A and/or broker B can
