Firstly, I hope I am taking the correct approach to requesting support.
I have artemis 2.39.0 running on Kubernetes with two statefulsets,
non-clustered but mirrored which works well enough for my requirements.
However: when I upgrade/or restart one of the pods, my logs are flooded with
2025-0
gt; [2]
> https://activemq.apache.org/components/artemis/documentation/latest/versions.html#upgrading-from-2-39-0
>
> On Mon, Apr 7, 2025 at 5:41 AM Kamara, George (RWS CIV)
> wrote:
>
>> Greetings.
>>
>> Im upgrading to 2.40.0 - and have read the minor changes th
Greetings.
Im upgrading to 2.40.0 - and have read the minor changes that are needed for
the upgrade (in this case HAWTIO_ROLE > ROLES), the instance itself works fine.
I’ve deployed in an environment to test and I’m not receiving the correct role
when using an external URL. The interface is
Hi,
We’re a lot further on our journey now and things are going relatively well.
I’ve implemented auto create expiry queue and this seems to be working well,
however. Momentarily our applications are not processing the expiry queues and
to that end, the journal is periodically filling up.
I di
Hi chad -
Sounds like a similar issue I had as well with 2.41.0 (presumably the version
you’re using)
In your jolokia-access.xml you can add the
"”
Tag to your restricts.
So the full file looks like
*://*
Hopefully that works for you.
On 1 Jul 2025, at 18:51, Chad S Lauritsen
wr
org/components/artemis/documentation/latest/message-expiry.html#configuring-expiry-addresses
>
> On Tue, Jun 24, 2025 at 4:12 AM Kamara, George (RWS CIV)
> wrote:
>
>> Hi,
>>
>> We’re a lot further on our journey now and things are going relatively
>> well.
>>
Hi All
Im doing a dry run of releasing 2.42.0
The user I am logged in has permission to send to all queues - but it looks
like the input box isn’t being rendered or it’s not accepting input.
Im using chrome and have tried incognito as well, but both result in the same.
Any pointers? - as alway
