= broker.getActiveMQServer();
> ActiveMQServerControlImpl manageBroker =
> activeBroker.getActiveMQServerControl();
> String connectionsList = manageBroker.listConnectionsAsJSON();
>
> Raymond
>
> On Thu, Jul 31, 2025 at 3:24 PM Justin Bertram
> wrote:
>
> > Use getRemoti
Use getRemotingService() on your ActiveMQServer instance and then
use getConnections() on the RemotingService you received. You'll receive
a Set that you can inspect.
Justin
On Thu, Jul 31, 2025 at 8:03 AM Modanese, Riccardo
wrote:
> Hi everyone,
> I’m looking for a way to inspect client conne
-keyalg RSA -keystore brokertest.ks
> > -storetype JKS -storepass keystore123 -keypass keypass123
> >
> > keytool only supports differing passwords for the JKS store type, even
> > though other store types like PKCS12 do support it as well.
> >
> > Let me know if
Query.isConfigurationManaged()"
> is null
>
>
>
> Philip
>
>
>
> On Tuesday, July 29th, 2025 at 19:43, Justin Bertram
> wrote:
>
> > Do you happen to have the stack-trace from the NPE? I'd like to add it to
> > the Jira for posterity'
> I hope this explains the issue better than my previous mails.
>
> Philip
>
>
>
>
>
> On Monday, July 28th, 2025 at 06:14, Justin Bertram
> wrote:
>
> > Do you have a sample project or anything that we can use to reproduce
> what
> > you're seeing?
Invitations sent.
Justin
On Tue, Jul 29, 2025 at 12:13 PM William Crowell
wrote:
> Good afternoon,
>
> Can you please send invites to the Apache Software Foundation Slack for
> the following email addresses?
>
> wcrow...@perforce.com
> jcar...@perforce.com
> tmune...@perforce.com
>
> Joe and T
issue better than my previous mails.
>
> Philip
>
>
>
>
>
> On Monday, July 28th, 2025 at 06:14, Justin Bertram
> wrote:
>
> > Do you have a sample project or anything that we can use to reproduce
> what
> > you're seeing? At this point, the only way I
trying to understand why the choice was made to have this
> `configurationManaged` property be
> nullable as it leads to an issue where the null value is attempted to be
> inverted which leads to an exception.
>
> I am using ActiveMQ Artemis 2.40.0
>
> Philip
>
>
&
The simplest way to investigate is with code that reproduces the problem.
Do you have a sample project or anything that we can use to reproduce what
you're seeing?
Also, what version of ActiveMQ Artemis are you using on the broker and the
client?
Lastly, can you clarify your use-case? It seems yo
cy (as I
> understood).
>
> Kind regards
> Maximilian
>
>
>
> Von:"Justin Bertram"
> An:users@activemq.apache.org
> Datum:07/11/2025 09:55 PM
> Betreff:[Ext] Re: Message Loss after Failover
> --
&g
I think this would be worth supporting.
I've got a couple of questions:
- Are you specifying a value for "keyStoreAlias"?
- How are you generating this keystore?
Justin
On Tue, Jul 22, 2025 at 7:45 AM Manuel K wrote:
> Hi all,
>
> we are using the STOMP protocol to send messages and Active
Slack invitation sent.
Justin
On Mon, Jul 21, 2025 at 7:09 AM Pierre-Jean Ciseau <
pierrejeancis...@gmail.com> wrote:
> Hi,
>
> I'd like to join the ActiveMQ Artemis Slack workspace to get support and
> engage with the community. Could you please share an invite link or let me
> know how to joi
I'm pleased to announce the release of ActiveMQ Artemis 2.42.0.
* Downloads:
https://activemq.apache.org/components/artemis/download/
* Complete list of updates:
https://activemq.apache.org/components/artemis/download/release-notes-2.42.0
I would like to highlight these improvements:
- Apply s
Invitation sent.
Justin
On Fri, Jul 18, 2025 at 6:08 AM Pareek, Chirag
wrote:
> Would you able to send me Slack channel invite please?
>
> Chirag Pareek
> Sr. Platform Engineer - Providing Platform Operations services managed by
> Kainos
> HMCTS Digital and Technology Services | HM Courts & Tr
Out of curiosity, does the behavior change if you just have a single broker
(i.e. eliminate clustering)? Typically it's best to validate behavior on
the simplest configuration and then add complexity in stages.
Justin
On Thu, Jul 10, 2025 at 10:05 AM wrote:
> Hello Community,
> In a failover c
Just to be clear about the way this works...
When a Core client using UDP discovery (i.e. connection url like
"udp://host:9876") it first simply listens for a connector broadcast via
UDP from the broker. Once the client receives the connector information it
uses that to connect. The configuration
When a Core client is configured for discovery [1] you just need the
corresponding broadcast-group on the broker(s) to broadcast a connector
that uses "sslEnabled=true". The client will receive that connector and use
it to connect to the broker.
You can do this with ActiveMQClient, e.g.:
Serv
The documentation you cited is specifically related to behavior when using
JDBC connection pooling.
Justin
On Fri, Jul 4, 2025 at 8:07 AM Sergey Fedechkin
wrote:
> Hi.
>
> In doc section
>
> https://activemq.apache.org/components/artemis/documentation/latest/persistence.html#configuring-jdbc-c
Neither JMS nor Core session objects are thread-safe so I would discourage
you from creating multiple consumers + listeners on a single session.
I would instead recommend you create a new session for each consumer.
Sessions are considered lightweight both in JMS and Core. This is even
noted in the
9682592497aa53064b106f4a...@sherwin.com?anonymous&ep=plink__;!!Cg_6rE7FVGHU6vd7!5RqjpK6haIsIkWPFBTOzq366DCs70X_WH9NDVHVJCUf-
> Vh9NAJs2K1yi687JxQZTqUIBxSnmMsLXoX5BeQV78r17NyHXGr2-JYIIbzx
> <https://urldefense.com/v3/__https://outlook.office.com/bookwithme/user/34f1d9682592497aa53064b106f4a...@sherwin.com?anonymous&a
What version of ActiveMQ Artemis are you using?
Justin
On Tue, Jul 1, 2025 at 11:52 AM Chad S Lauritsen
wrote:
> Hello activemq list.
>
> New subscriber here.
>
> We have ActiveMQ artemis running in Kubernetes clusters. I would like to
> expose the Artemis console using a Kubernetes Ingress. B
Any update on this, Erik?
Justin
On Fri, Jun 13, 2025 at 10:53 AM Devriendt, Erik
wrote:
> That might be acceptable, depending on the time needed to detect the
> disconnection and perform the failover.
> I will do some tests next week.
>
> -Original Message-
> Fr
This documentation [1] might be helpful. It basically explains what Herbert
mentioned. In short, you can ensure expired messages are dropped by
unsetting the expiry-address.
Justin
[1]
https://activemq.apache.org/components/artemis/documentation/latest/message-expiry.html#configuring-expiry-addr
You can use the upgrade tool to do everything at once.
Justin
On Tue, Jun 17, 2025 at 2:41 PM Edson Richter
wrote:
> Hi!
>
> Do I need to execute manual upgrade version by version (2.22.0=>2.23.0,
> 2.23.0=>2.24.0, etc), or can I use the upgrade tool to upgrade direct from
> 2.22.0 to 2.41.0?
10 times today.
>
> Thank you both!
>
> > On 24 Jun 2025, at 16:45, Justin Bertram wrote:
> >
> > LET OP! Deze e-mail komt van buiten de organisatie. Klik niet op links
> en open geen bijlagen tenzij je de afzender herkent en weet dat de inhoud
> veilig is.
> >
Since I can't see your screenshot I'm not sure about the details of your
question. However, I can say a couple of things which may be helpful...
The notification address is where management notifications are sent. You
can read more about management notifications in the documentation [1].
Queues n
Try adding this to etc/log4j2.properties:
logger.hawtio-auth.name=io.hawt.system.Authenticator
logger.hawtio-auth.level=DEBUG
The logging will go to the console and to artemis.log by default.
Justin
On Fri, Jun 20, 2025 at 8:28 AM John, Richard
wrote:
> Hi.
>
> Having trouble logging
This has been addressed a few times on this list [1] [2], and plans haven't
changed since then. In short, there are no plans to remove OpenWire
protocol support from ActiveMQ Artemis.
To be clear, how commercial vendors deploy ActiveMQ components and what
particular features they support is 100% u
> No, the producer sends messages to a queue "cms.test.c.client.queue", the
> consumer reads from that queue.
To be clear, I don't believe these two use-cases are directly comparable
due to the difference between pub/sub & point-to-point semantics, but I
digress.
Regarding your federation configu
I think I see now, but I want to confirm since I've not seen this kind of
configuration before. You've intentionally configured 2 federation
connections in a redundant fashion so that each connection is sending the
same message resulting in duplicates on the target. Is that correct?
Are you using
> Is it possible to set the Artemis property _AMQ_DUPL_ID in a MQTT client?
Technically speaking, it is possible to set the property _AMQ_DUPL_ID in a
MQTT client. However, as you note, that property won't be treated the same
as in other protocol implementations.
> It seems to me that MQTT v5 Use
"q.#" queue would remain, AFAICT?
That's correct.
Justin
On Sun, Jun 8, 2025 at 8:43 AM Fredrik Jonson wrote:
> Justin Bertram wrote:
>
> > Have you considered creating an individual consumer for each destination
> > and either using management notifications or po
Session objects are not
thread-safe.
Justin
[1]
https://github.com/apache/activemq-artemis/blob/main/docs/user-manual/wildcard-routing.adoc
[2]
https://github.com/apache/activemq-artemis-examples/blob/main/examples/features/standard/topic-hierarchies/src/main/java/org/apache/activemq/arte
I think the first thing to remember here is that the functionality you're
using is underpinned by wildcard *routing* [1] which is similar, but not
equivalent, to wildcard consuming. Wildcard routing was mainly designed for
multicast use-cases (e.g. topic hierarchies) although it will work with
anyc
On Wed, Jun 4, 2025 at 11:54 AM Franck Malka wrote:
> I upgraded from 2.14 to 2.41
> in 2.14 name# was working fine.
>
>
>
> On Wed, Jun 4, 2025 at 7:24 PM Justin Bertram wrote:
>
> > Are you referring to the "match" of an "address-setting"? If
ard-syntax.html#wildcard-syntax
On Wed, Jun 4, 2025 at 11:04 AM Franck Malka wrote:
> I sorted it out by replacing the match prefix from "name#" to "name*"
>
> On Wed, Jun 4, 2025 at 6:59 PM Justin Bertram wrote:
>
> > Can you be more specific about where e
The Artemis test-suite is full of examples of clustered, embedded brokers.
I'd recommend looking at
org.apache.activemq.artemis.tests.integration.cluster.distribution.SimpleSymmetricClusterTest.
You'll have to dig through some scaffolding for the test-suite, but
everything you need should be there.
Can you be more specific about where exactly you're looking? If possible,
steps to reproduce the behavior you're observing would be ideal.
Justin
On Wed, Jun 4, 2025 at 4:18 AM Franck Malka wrote:
> Hi, All
>
> In my broker.xml I configured different address-settings for different
> address na
I've not seen this specific behavior before. I'm not sure why it would do
that.
To be clear,
org.apache.activemq.artemis.spi.core.protocol.RemotingConnection#getRemoteAddress
is basically just a wrapper around io.netty.channel.Channel#remoteAddress
[1] so the exact behavior here will be determined
Couple of thoughts here:
- Necessary properties and/or payload should really be set by the
producers themselves. This should be part of the messaging "contract" (e.g.
like an API) used to govern communication between application components.
- One of the main strengths of asynchronous messaging i
The information you're looking for is on our website [1] (linked from the
Apache->Security menu item). In short, you should email secur...@apache.org.
Justin
[1] https://activemq.apache.org/security-advisories
On Thu, May 29, 2025 at 3:48 PM Mau, I-Min
wrote:
> I am definitely NOT going to se
Done.
Justin
On Thu, May 29, 2025 at 8:36 AM Chokha Palayamkottai
wrote:
> Hi,
> Could you please send me an invite to slack as well? Thanks.
>
> Best,
> Chokha.
>
> On Thu, May 29, 2025 at 9:34 AM Justin Bertram
> wrote:
>
> > Done.
> >
> >
>
Done.
Justin
On Thu, May 29, 2025 at 6:33 AM André António Santos Antunes Conrado <
andre.conrad...@gmail.com> wrote:
> Hi,
>
> Could you send me an invite to use Slack?
>
> Thanks!
>
> ---
> André Antunes Conrado
>
The broker delegates log file handling to Log4j2. The default
log4j2.properties uses a RollingFile appender for "artemis.log," and I
believe this behavior is controlled by the value of the "append" property
which is not set and defaults to true. Of course, it's always possible
you're hitting a bug.
mation here but also reach out to the Cassandra
> community.
>
> Thank you.
>
>
> Jason
>
>
>
> From: Justin Bertram
> Sent: Tuesday, May 27, 2025 11:35 AM
> To: users@activemq.apache.org
> Subject: Re: Apache ActiveMQ Classic
s, the Address size of address TEST is 108900. Can you clarify how
> this value is calculated?
>
> As paging starts when the max size bytes configured for the address TEST
> exceeds this value, I want to understand this to configure the limit
> accordingly.
>
>
>
>
>
>
Can you clarify your use-case?
Are you attempting to use Apache Cassandra as the storage mechanism for
ActiveMQ Classic? If so, you'll need to implement a Cassandra-based
persistence adapter since it doesn't provide a JDBC driver or other means
of integration. It's possible such an adapter already
> How is address size calculated?
Address size, as in the value reflected in the "Address Size" property of
the corresponding Address Control, is calculated by inspecting each message
as it is sent to an address and adding its individual size to a running
total. It is directly related to paging th
Here's what I understand about your problem based on the description you
provided:
- Everything was working fine
- You patched your OS
- Now the primary and backup are no longer connecting
Is that correct? If so, have you tried reverting the OS patches to see if
that resolves the problem?
Ju
One simple way to determine the corresponding properties for any XML
configuration is to use the exportConfigAsProperties management operation.
Further details are available in the documentation [1].
Justin
[1]
https://activemq.apache.org/components/artemis/documentation/latest/management.html#s
ole.
Justin
On Thu, May 15, 2025 at 9:57 PM Jean-Baptiste Onofré
wrote:
> Hi
>
> I agree with Justin. Name change also has an impact on ASF trademarks.
> So, a name change would require approval from PMC and a namesearch.
>
> Regards
> JB
>
> On Wed, Apr 30, 2025 at 10
> Am I mistaken about this, or have missed a place where I can set
IP_MULTICAST_TTL for the broadcast socket?
You are not mistaken. Setting this option is not currently supported in the
native UDP implementation.
> If not, what's the way to request a enhancement for Artemis that would
include thi
would be specific
> to artemis-jakarta-client, text message. Since it is a safety feature it
> would be a configuration that consumers can set, and if the TextMessage is
> above that threshold a JMSException would be thrown. I can work on this PR.
>
> Den tors 1 maj 2025 kl 21:46 skrev T
on issue or bug with NFS or network related issue
> as you stated.
>
> Regards,
>
> William Crowell
>
> From: Justin Bertram
> Date: Thursday, May 1, 2025 at 2:27 PM
> To: users@activemq.apache.org
> Subject: Re: Apache Artemis 2.40.0: Strange File Locking Behavio
an be subject
> to DLQ policy on the broker side.
>
> On Wed, Apr 30, 2025, 21:50 Justin Bertram wrote:
>
> > If the message was sent as a "large" message or converted into a large
> > message by the broker (e.g. if it exceeded the journal-buffer-size) then
> i
> am verifying the Linux kernel build version, but it should be very recent.
>
> Regards,
>
> William Crowell
>
> From: Justin Bertram
> Date: Thursday, May 1, 2025 at 12:57 PM
> To: users@activemq.apache.org
> Subject: Re: Apache Artemis 2.40.0: Strange File Locking Be
ctivemq.artemis.core.server.impl.FileLockNodeManager] state: L
> (THIS MEANS ACTIVE)
> 2025-05-01 15:07:05,184 DEBUG
> [org.apache.activemq.artemis.core.server.impl.FileLockNodeManager] acquired
> primary node lock state = L
> 2025-05-01 15:07:05,186 DEBUG
> [org.apache.activemq.artemis.core.server.impl.FileLockNodeManager] touch
025, 6:32 am Niraj Kumar Rohit, <
> nirajkumarro...@gmail.com>
> wrote:
>
> > Before we hav hornetq ,now we have to replace hornetq with artemis 2.19.1
> >
> > On Tue, 15 Apr, 2025, 12:22 am Justin Bertram,
> > wrote:
> >
> >> To clarify, you h
Would you mind turning on DEBUG logging for
org.apache.activemq.artemis.core.server.impl.FileLockNodeManager [1],
reproducing, and uploading the full logs someplace accessible?
Regarding your NFS mount options...I was perusing the NFS man page [2] and
saw this note about noatime & nodiratime:
>
>
> --
> *From:* ski n
> *Sent:* 25 April 2025 20:41:36
> *To:* users@activemq.apache.org
> *Subject:* Re: ArtemisMQ branding
>
> tbh ArtemisMQ sound pretty neat.
>
> Raymond
>
> On Fri, Apr 25, 2025 at 8:35 PM Justin Bert
the source code and at the logs - it seems that group buckets are "used"
> inside the queue, but are not taken into account by the grouping handlers?
> Or, in other words, why configuring n group buckets I end up having n group
> buckets on each broker rather than on the entire
If the message was sent as a "large" message or converted into a large
message by the broker (e.g. if it exceeded the journal-buffer-size) then it
can be streamed from the broker in chunks via JMS as noted in the
documentation [1]. However, if the message is not "large" then the entire
message will
I think this bit from the example's documentation is relevant:
With a symmetric cluster, the cluster is homogeneous, i.e. each node is
configured the same as every other node, and every node is connected to
every other node in the cluster.
Given that an HA pair of brokers are explicitly not con
šper Čefarin
wrote:
> Ah, I see - I must have mixed the names up somewhere along the way.
> This makes a bit more sense now.
>
> However there's still 2 distinct broker versions, right? How about just
> putting artemis on the bottom, or something of the sort?
>
> ___
t; Best Regards
> Shiv
>
> -Original Message-
> From: Justin Bertram
> Sent: 23 April 2025 10:38 PM
> To: users@activemq.apache.org
> Subject: Re: Issue in artemis mask/unmask
>
>
>
> Unverified Sender: The sender of this email has not been verified. Review
&
x27;s an example of what I had in mind ...
> https://imgur.com/DckgmsN
>
>
>
> --
> *From:* Justin Bertram
> *Sent:* 25 April 2025 16:27:58
> *To:* users@activemq.apache.org
> *Subject:* Re: ArtemisMQ branding
>
> There are no plans to change
There are no plans to change any branding for the web console or Artemis
generally.
Justin
On Fri, Apr 25, 2025 at 9:17 AM Gašper Čefarin
wrote:
> Hi,
>
>
> I noticed some small issues with the favicon for the new artemis console,
> and before I do any pull requests I just wanted to ask if the
>
>
>
>
> I have also tried with negative regex and moving destroyQueue method to
> the key'ed match. Still doesn't work.
>
> Are there any other methods how to limit destroyQueue functionality just
> on particular set
The underlying code uses regular expressions so doing so in management.xml
should also work. That said, I'd recommend using this key instead of what
you originally proposed:
key="queue=(DLQ|ExpireQueue)"
Justin
On Tue, Apr 22, 2025 at 4:39 AM Vilius Šumskas
wrote:
> Hello,
>
> as an addit
I think you're likely hitting ARTEMIS-4154 [1].
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-4154
On Wed, Apr 23, 2025 at 8:21 AM Shiv Kumar Dixit
wrote:
> Hi team,
> We are facing an issue in using artemis mask/unmask for certain literals.
> When such literals are present as part
> Critical: CVE-2016-127 —
https://nvd.nist.gov/vuln/detail/CVE-2016-127
The link indicates the CVE impacts "Spring Framework through 5.3.16."
However, ActiveMQ Classic 5.19.0 ships with Spring 5.3.39. This seems like
a false positive from your scanner.
Justin
On Mon, Apr 21, 2025 at 10
on regarding createDurableQueue
> permissions requirement. Is it required *by the consumer*? Can those topic
> queues be created by the producer, or does it go against pub/sub model?
>
> --
> Vilius
>
> -----Original Message-
> From: Justin Bertram
> Sent: Wednes
> Do these clients need to be of a particular version, or is native
redirection implemented using native protocol specification. E.g. any AMQP
0.9 client will work?
Just to avoid any confusion...AMQP 0.9 isn't supported. Only 1.0 is
supported.
Justin
On Fri, Apr 18, 2025 at 6:14 AM Vilius Šumsk
that makes sense. If client ID and subscription name is known in
> advance, would you advise to create queues via management API in disabled
> state and then enable after consumer comes online, like suggested by
> Alexander?
>
> --
> Vilius
>
> -----Original Message-
> ...I’m not 100% sure if this requirement comes from Qpid library which we
are using, or Camel, or is it a requirement for JMS subscribers in
general...
This is a requirement for JMS topic subscriptions in general. See the
documentation [1] for more details.
> Is there a way to limit amount of q
> [a] MY TEST: broker V2.38 configuration has no effect to MQTT 3.1.1 client
> keep-alive connection (always disconnects after 180 seconds).
> [b] DOUBTS: In MQTT 3.1.1, should the client configuration [3.1.2.10 Keep
> Alive] work independently of the broker configuration file?
>
>
artemis.core.remoting.impl.ssl.DefaultOpenSSLConte
> > > xtFactory.getServerSslContext(DefaultOpenSSLContextFactory.java:60)
> > > > at
> > > >
> > > org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptor.loa
> > > dSSLContext(N
s loaded.
> If attachments are not allowed here, I can upload to some file sharing
> service.
>
>
> пн, 7 апр. 2025 г. в 21:34, Justin Bertram :
>
>> I tried to reproduce this using a fresh instance of 2.40.0 with 2,500
>> queues defined in broker.xml (thanks to a bash
апр. 2025 г. в 20:56, Justin Bertram :
>
> > Thanks for the thread dumps!
> >
> > I see that in all the "after_logon" thread dumps there is a thread like
> > this working:
> >
> > "qtp368040556-79" #79 prio=5 os_prio=0 cpu=3462.39ms
is on java 8.
>
> On Mon, 14 Apr, 2025, 6:42 pm Justin Bertram, wrote:
>
> > > i want to enable the web console in artemis 2.19.1.
> >
> > I answered a question similar to this on Stack Overflow [1] awhile back
> > that should give you a good idea of what'
age grouping (i.e. as soon as I don't send messages with
> group id) redistribution works like a charm.
> Is message redistribution supposed to work even when message grouping is
> used?
>
>
> Mirko
>
> From: Justin Bertram
> Sent: Friday,
Best Regards,
> > > Vilius
> > >
> > > -Original Message-
> > > From: Andy Taylor
> > > Sent: Thursday, April 10, 2025 9:15 AM
> > > To: users@activemq.apache.org
> > > Subject: Re: 2.40.0 HAWTIO console design
> >
ly tens
> > of
> > thousands) of such external users using these temporary queues, so
> > this method will be less complex for us to control. We will accept the
> > possible low security risk.
> > Lockdown method you have proposed is sound, but giving some internal
> >
to start the artemis.
>
> Thanks
> Niraj
>
>
>
> On Wed, Apr 9, 2025 at 8:40 AM Justin Bertram wrote:
>
> > In the code you shared I don't see any evidence that you're properly
> > configuring your brokers to cluster. A pair of brokers using replication
>
ld you please suggest an approach to address my requirement?
> Thanks.
>
>
>
> From: Justin Bertram
> Sent: Friday, April 11, 2025 7:29:09 PM
> To: users@activemq.apache.org
> Subject: Re: Clustered Grouping: how to make sure that each queue on t
Before we get into the details of your use-case I have a few questions...
1) Have you conducted benchmark tests and demonstrated conclusively that
you cannot meet your performance goals with a single broker (or HA pair of
brokers)? If so, can you share any details about your testing and the
resul
> If so does it mean the ack failed thus the message is not acked and will
be delivered to the consumer again in the new session?
Yes.
> Attached is the full log
Looks like the attached log didn't make it through the list filters. Maybe
try pasting it somewhere (e.g. here [1]) and providing a li
it goes. Post that I will collect thread dumps and share for
> further analysis.
>
> On the side note - if there any article or whitepaper from community on
> how to handle (D)DoS attack on Artemis broker?
>
> Best Regards
> Shiv
>
> -----Original Message-
> From: J
or, will it protect against
> misbehaving producer/consumer? I understood that it is only good enough to
> restrict good connections.
>
> Best Regards
> Shiv
>
> -Original Message-
> From: Justin Bertram
> Sent: 09 April 2025 07:28 PM
> To: users@activemq.apac
It's worth noting that there have been 2 independent releases of the
console that was integrated into and shipped with 2.40.0. Both of these
releases were announced on this list [1] [2]. Both announcements included a
notification that it would replace the existing console. The first release
was in
> I know I may get some hate for this...
No hate here! We love to get feedback from users - good, bad, or
indifferent. So, thanks for speaking up.
> ...it's more JMX and less Artemis...
Here's a breakdown of the relevant screens, what they used to be and what
they are now...
- Artemis: This sc
After some back and forth we have decided to use random UUID
> temporary replyTo queues for now. Until PCI DSS or similar compliance will
> require us to completely separate our clients.
>
> --
> Vilius
>
> -----Original Message-
> From: Justin Bertram
> Sen
In the code you shared I don't see any evidence that you're properly
configuring your brokers to cluster. A pair of brokers using replication
need a valid cluster to discover each other. This is noted in the
documentation [1] which states, "A proper cluster configuration is required
as a pre-requis
ues
> sitting on disk. Another penalty I suppose is queue scanning every
> "address-queue-scan-period"? If we have thousands of queues and the scan
> needs to check every queue for messages and consumer count I suppose this
> is also relatively slow operation?
>
> --
>
of SSL handshake errors as we could see lot of
> 'AMQ224088: Timeout (10 seconds) on acceptor "artemis-ssl-customer" during
> protocol handshake with /1.2.3.4:62403 has occurred.' Where clients are
> trying to connect back. After some time it got restarted with OOM.
>
ote:
> Hi Justin
>
> That indeed did resolve the problem!
>
> Perhaps useful to include this in the upgrade notes.
>
> Thank you very much!
>
>
>
>
> > On 7 Apr 2025, at 22:53, Justin Bertram wrote:
> >
> > LET OP! Deze e-mail komt van buiten de o
I tried to reproduce this using a fresh instance of 2.40.0 with 2,500
queues defined in broker.xml (thanks to a bash script), but the console
loaded in just a few seconds.
I then created a fresh instance of 2.39.0 with 2,500 queues defined in
broker.xml. Then I ran "artemis data exp" to export the
You may need to add to your etc/jolokia-access.xml. A PR
[1] recently updated the upgrade documentation [2].
Justin
[1] https://github.com/apache/activemq-artemis/pull/5612
[2]
https://activemq.apache.org/components/artemis/documentation/latest/versions.html#upgrading-from-2-39-0
On Mon, Apr 7
as a replyTo queue (not all temporary queues exist at all
> times obviously). If performance impact is considerable, can it be
> alleviated, by let's say, enabling auto-delete-queues/auto-delete-addresses
> only on replyTo queues?
>
> --
> Vilius
>
> -O
> When I connect using the Ingress route URL, I get the blank screen, but
authentication is still fine.
This sounds like a problem with your etc/jolokia-access.xml configuration.
How is it configured? If the problem was related to the HAWTIO_ROLES
configuration I don't think it would work in any c
1 - 100 of 1246 matches
Mail list logo
