thanks a lot Dan... I don't think the issue was replication... it was about how the address was created... , but I can see Justin fixed it.. nice one!
I recommend you specifying the routing type when creating the addresss on 2.0 though. I woud use 2.1 anyways.. I'm finishing up and I will start the release vote this afternoon. On Tue, May 2, 2017 at 2:04 AM, Dan Irwin <rummymob...@gmail.com> wrote: > Hello Clebert, > > Thanks for your response. > > I have just built the latest code from git, and this issue persists. (Did a > clone, mvn build, installed, created new brokers) > > I just created https://issues.apache.org/jira/browse/ARTEMIS-1137 with the > details. > > Some more info > 1.5.4: OK > 2.0.0: Exception on master restart > GIT: Exception on master restart > > Thank you > > > On Tue, May 2, 2017 at 1:44 PM, Clebert Suconic <clebert.suco...@gmail.com> > wrote: > >> Can u try master (upcoming 2.1) >> >> >> >> I'm about to start a release process as soon as I fix a final test. >> >> If u can still hit the issue. Please give us instructions. >> >> >> >> On Mon, May 1, 2017 at 11:00 PM Dan Irwin <rummymob...@gmail.com> wrote: >> >> > Hello, >> > >> > I am playing with Artemis 2. I have a fairly simple 2 node configuration >> > with replication and failover. >> > >> > I suspect there is a replication bug. Stopping and restarting the master >> > results in: >> > >> > ERROR [org.apache.activemq.artemis.core.server] AMQ224000: Failure in >> > initialisation: java.lang.IllegalArgumentException: Collection is empty >> > at java.util.EnumSet.copyOf(EnumSet.java:174) [rt.jar:1.8.0_121] >> > at >> > >> > org.apache.activemq.artemis.core.postoffice.impl. >> SimpleAddressManager.lambda$updateAddressInfo$0( >> SimpleAddressManager.java:240) >> > [artemis-server-2.0.0.jar:2.0.0] >> > >> > >> > I have had a look around, and I didn't notice any issues for this. >> However, >> > I did notice on the development list that a 2.0.1 or 2.1 is due shortly, >> > and has fixes for replication issues. >> > >> > Is this a known issue, and will it be fixed in the next 2.whatever >> release? >> > >> > Thank you >> > >> -- >> Clebert Suconic >> -- Clebert Suconic