If you are talking about amqp consumers staying in the queue after
connection killed i am currently Investigating.
I should have a fix but I don’t have a test. So I would love to see a test
reproducing it as I took 4 arduous days trying to reproduce it. I could not
so far.
On Thu, Oct 19, 2023
Hi Team,
Is there any ideas on what is wrong with replication?
Any suggestions on tuning timeout parameters?
Which parameter should I configure to increase timeout which appears in this
log message?
WARN [org.apache.activemq.artemis.core.server] AMQ222137: Unable to announce
backup, retrying
Hi Justin,
It is a client issue so I don’t have a readily available reproducer. I can ask
them to provide a sample .Net app which will be able to produce the issue.
Best Regards,
Shiv
-Original Message-
From: Clebert Suconic
Sent: Thursday, October 19, 2023 12:44 AM
To:
Hi All,
We have configured Artemis 2.31.0 symmetric cluster in the test environment.
Example of cluster configuration on one of the nodes:
amq1-connector
1000
5000
5
5000
500
1.0
5000
-1
-1
true
ON_DEMAND
1
amq2-connector
Hi Domenico,
> maybe this issue is due to the cache, see
> https://github.com/apache/activemq-artemis/blob/2.31.0/artemis-server/src/main/java/org/apache/activemq/artemis/core/security/impl/SecurityStoreImpl.java#L409
>
> Could you try to clear the authentication cache using the operation
>
Hi Aleksandr,
maybe this issue is due to the cache, see
https://github.com/apache/activemq-artemis/blob/2.31.0/artemis-server/src/main/java/org/apache/activemq/artemis/core/security/impl/SecurityStoreImpl.java#L409
Could you try to clear the authentication cache using the operation
Hi Domenico,
> this should only happen if the user logged in the console doesn't have the
> required roles to send messages to the desired addresses (check the
> security-settings in broker xml).
Current user has permissions to send message.
If we turn off "use current logon user" checkbox and
