Hi Andrea,
the improvement to configure all connection-router settings by using broker
properties should be quite easy, I did a quick POC[1]. Could you explain
why your use case requires a cache?
[1]
https://github.com/brusdev/activemq-artemis/commit/d63883aa0680cf7f837a18964e8ed70b6bdda4c9
Rega
Hi,
I'm using Artemis v2.27.1.
I have 2 replicating clusters, both consisting of 1 master and 1 slave node.
One of them does not offer the option to send a message through the artemis web
console.
How can i troublehsoot this?
Restart did not help.
Options missing are:
Delete queue
Send message
B
Hello,
Im trying to understand the behavior, because the scheduledb.data file
continues to grow no matter how many messages are consumed.
What am I missing?
Consider this,
ActiveMQ Classic 5.16.3, OpenJDK 1.8.0_392 , Ubuntu 22.04
2 Queues 1 and 2
Each queue 10 messages.
Queue1 All messages c
Hi Gašper,
the missing queue tabs are shown only if the logged in user has the related
management rights: destroyQueue, sendMessage, browse and countMessages.
Could you compare the management.xml of the 2 live brokers?
Regards,
Domenico
On Wed, 3 Jan 2024 at 15:27, Gašper Čefarin
wrote:
> Hi,
Hi Domenico,
many thanks for your quick reply.
We are investigating different Connection Router strategies (e.g. based on
CLIENT_ID, SNI_HOST, SOURCE_IP) and we would be interested into enabling a
Connection Router Cache for speed up the finding of the target broker without
having to apply the p
Hi Team,
We are using tika-app-1.22.jar and it found transitive dependent
org.apache.activemq:activemq-osgi:5.15.11. We have found vulnerability issue
with CVE-"CVE-2023-46604" with Score 10.0 that is critical.
Could you share the impact analysis and mitigation for this CVE.
Thanks
