Hi,
I have an ActiveMQ (5.16.2/JDK11) broker with persistence message (kahadb).
We are using a deadletter strategy to clean messages older than 7 days
but we can see that some of the older message are not clean up and we
don't have any error/warning message in the logs...
Here the config.xml
Hi,
can you share your JVM configuration and your activemq.xml config file?
Regards,
François
On 03/08/2023 09:04, Amy Hartland (DHCW - Integration Services) wrote:
Hello,
We are currently using apache-activemq-5.15.3. We are noticing some issues with
java heap space.
Wrapper log;
INFO |
them for even more gains.
In my opinion it is a compelling strategy, but one that speaks more about
finances than the technical merits of either broker.
Justin
On Fri, Sep 30, 2022 at 7:46 AM fpapon wrote:
Hi,
Thanks for all these feedbacks, this is very interesting!
When searching on the web, I
Hi,
Thanks for all these feedbacks, this is very interesting!
When searching on the web, I can see that most of SaaS providers provide
ActiveMQ Classic (AWS, Azure, Oracle) not because of performance but
more because of stability of the solution.
I'm not saying that Artemis is not stable
Hi JB,
I think it make a lot of sense to focus on this points and I will be
more than happy to contribute!
There is a very large community of users around the ActiveMQ 5.x and
it's still very widely use in production environment.
I'm not sure that the users actually understand the difference bet
