Re: ActiveMQ not recovered automatically from error "Persistent store is Full" when system become normal.

Hi all, Able to see a debugging tool GitHub - Hill30/amq-kahadb-tool to view kahadb data log and e nabling TRACE level logging for kahaDB gave some insight about the issue to sort it out. Referred: https://activemq.apache.org/why-do-kahadb-log-files-rema

RE: Questions around security and permissions

Correct. This is exactly what we are doing. By the way, as far as we found out, permissions created on-demand will be stored in the journal independently which user/role storage mechanism you choose. That was one more reasons for us to go with ActiveMQBasicSecurityManager because we won't have

Re: Questions around security and permissions

Thanks all. This sounds like a viable solution to our problem. Just to be sure: If I want to set permissions per user I also have to create a dedicated role per user because permissions can only be granted to roles? Thanks, Thorsten Am Donnerstag, dem 28.04.2022 um 09:00 -0500 schrieb Justin Ber

R: Artemis 2.21+ - MQTT devices don’t receive the messages matching their subscriptions

>From my understanding our previous subscription “#” Should be changed into 2 different subscriptions: “#” “$EDC/#” Now the $EDC/# is not working due to ARTEMIS-3801 right? If so I think it’s not a big problem we should manage 2 different subscriptions instead of one. Thanks Da: Ju

ActiveMQ 5.16.1 - CRL in crlPath in sslContext is not used

Hi, We use ActiveMQ version 5.16.1, and we are trying to add a crlPath to the sslContext in order to revoke a client certificate. However, we observed that the CRL is not used after restarting AMQ, and that it is still possible to use the certificate with the serial number in the CRL to connect