Re: Artemis 2.30 cluster split brain due to sudden credit consumption

2023-08-25 Thread Justin Bertram
> We don't have HA enabled. In ActiveMQ Artemis the idea of "split-brain" [1] is predicated on an HA configuration. In short, it's what we call what happens when both a primary and backup server are active at the same time serving the same messages to clients. Given that you're not using HA then "

Re: building docker image following the guide - not working for me - I'm sure I'm missing something

2023-08-25 Thread Mike Williams
Hey Justin I think it's a good point that no one has requested it (until now) - so don't waste time accommodating just me. I'm sure you have better things to do! If I can build it myself and work on contributing my findings for an update to the docs "For Ubuntu (Build for linux ARMv7/ARM64)" the

Re: building docker image following the guide - not working for me - I'm sure I'm missing something

2023-08-25 Thread Justin Bertram
If you need an arm64 image we could add that to the release. To my knowledge nobody has requested this. Justin On Fri, Aug 25, 2023 at 4:29 PM Mike Williams wrote: > Hi Clebert > > Thanks for feedback. I've seen the docker hub image that Justin posted and > we're using it for our initial local

Re: Messages balance between two MQTT connections open with same clientId on different acceptors

2023-08-25 Thread Justin Bertram
This should be resolved as a corollary change in the next release via ARTEMIS-966 [1]. The solution is close to the second option you proposed. Clients using different acceptors will *not* be able to connect concurrently. However, the link-stealing behavior will be based on whatever is configured

Re: building docker image following the guide - not working for me - I'm sure I'm missing something

2023-08-25 Thread Mike Williams
Hi Clebert Thanks for feedback. I've seen the docker hub image that Justin posted and we're using it for our initial local tests (many thanks Justin). I need an image for arm64 arch for my lab setup to try a k8s deployment so I'm trying to build one following the guide but doesn't seem to work.

Re: building docker image following the guide - not working for me - I'm sure I'm missing something

2023-08-25 Thread Clebert Suconic
Docker run is the entry point for the image. There is an image for artemis now that Justin uploaded. On Fri, Aug 25, 2023 at 3:01 PM Mike Williams wrote: > Hi All > > I've been following this guide to try and build a local docker image: > https://github.com/apache/activemq-artemis/tree/main/ar

Re: Artemis 2.30 cluster split brain due to sudden credit consumption

2023-08-25 Thread Clebert Suconic
Do you have the clock of your system in sync ? Just out of coincidence I had some issues the other day on an user and it turned out to be that. Check the time at your systems. On Fri, Aug 25, 2023 at 3:22 PM Stefano Mazzocchi < stefano.mazzoc...@gmail.com> wrote: > Hi Justin, thx for your resp

Re: Artemis 2.30 cluster split brain due to sudden credit consumption

2023-08-25 Thread Stefano Mazzocchi
Hi Justin, thx for your response! Find my answers inline below. On Thu, Aug 24, 2023 at 8:43 PM Justin Bertram wrote: > Couple of questions: > > - What high availability configuration are you using and at what point > does split brain occur? > We don't have HA enabled. Artemis is used as an a

building docker image following the guide - not working for me - I'm sure I'm missing something

2023-08-25 Thread Mike Williams
Hi All I've been following this guide to try and build a local docker image: https://github.com/apache/activemq-artemis/tree/main/artemis-docker I downloaded the 2.30.0 tag tgz and built an image but when I start it I get the following error: "/docker-run.sh: line 42: /opt/activemq-artemis/bin/

Messages balance between two MQTT connections open with same clientId on different acceptors

2023-08-25 Thread andrea bisogno
Hi support, I observed an unexpected behavior while testing the Artemis Broker (v 2.29.0): if we have two MQTT connections with the same clientId open at the same time (possible only with two clients opening two different connections with same clientId to different MQTT acceptors/ports, regardl