ActiveMQ Artemis fully implements the JMS specification so any client using
JMS (e.g. Apache Camel) should work without issues. For what it's worth,
Artemis ships with an example [1] using Apache Camel for bridging messages
between a 5.x broker instance and an Artemis instance.
The ActiveMQ 5.x ha
Hi Tim,
Thanks for your suggestions.
Saying that, moving to ActiveMQ Artemis would be the ideal option. I'm also
not sure whether all the features being used by us (camel routes are used to
produce and consume JMS messages) with ActiveMQ 5.14.4 will be available in
ActiveMQ Artemis 2.5.0.
>From
On Wed, Apr 4, 2018, 11:51 PM SubashKunjupillai
wrote:
> Hi,
>
> We have been using ActiveMQ 5.x (upgraded to 5.14 last year) for our
> product
> which is in production for 3years. We have been facing stability issues
> with
> replicated LevelDB store(it was deprecated by community after we went
Hi,
We have been using ActiveMQ 5.x (upgraded to 5.14 last year) for our product
which is in production for 3years. We have been facing stability issues with
replicated LevelDB store(it was deprecated by community after we went live
with LevelDB, we have stuck to it as we accomplished HA through r
