esendet: Montag, 13. März 2023 12:28
> An: users@activemq.apache.org
> Betreff: Re: cloud-native deployment
>
> Thanks Vilius and Ephemeris for your input.
>
> Regards,
> Prateek Jain
>
> --
Thanks Vilius and Ephemeris for your input.
Regards,
Prateek Jain
--
EXPECTATION : Causes all troubles..
--
On Mon, Mar 13, 2023 at 11:07 AM Vilius Šumskas
wrote:
> Hi,
Hi,
check the mailing list archives. This question comes up regulary.
--
Vilius
-Original Message-
From: prateekjai...@gmail.com
Sent: Monday, March 13, 2023 11:46 AM
To: users@activemq.apache.org
Subject: cloud-native deployment
Hi All,
How are you? I am trying to deploy arte
Hello again.
As I said, we use JDBC persistence, and in a 2 instances
configuration, the two brokers compete to gain the leadership on
the DB lock table. The only special configuration of the broker
is setting the JDBC datasource to reoplace the KahaDB default
Thanks for the feedback, Ephemeris. Did you do anything special to avoid
split brain scenarios?
Regards,
Prateek Jain
--
EXPECTATION : Causes all troubles..
--
On Mon, M
Hello.
We've not experienced deployment of Artemis yet, but for our last works
we use "classic" ActiveMQ 5.17.x on our K8s clusters. Our PODs are
stateless, since we use JDBC (postgresql) persistence instead of KahaDB.
We've also tested 2 PODs configurations.
In both cases Openwire and HTTP
