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
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
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 wrote:
> Hello,
>
> I am playing with Artemis 2. I have a fairly simple 2 node configurat
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.Ille
So it seems you have four brokers in your network of brokers: A1, B1, A2,
B2. They are all live (that is, none are part of a master/slave pair where
the slave is idle) with duplex connections like this
A1 <> B1, B1 <> B2, B2 <-> A2, A2 <> A1.
How many messages are "getting lost"? W
Hi,
We have 2 network-of-brokers with a failover-configuration, but we're having
performance-problems and loosing messages. Clients connect to HostA1 and
HostA2. All brokers run 5.8 stable, only persistent messages using KahaDB:
HostA1:
uri="static:(ssl://HostA2:61616)" duplex=
Hi,
We have 2 network-of-brokers with a failover-configuration, but we're having
performance-problems and loosing messages. Clients connect to HostA1 and
HostA2. All brokers run 5.8 stable, only persistent messages using KahaDB:
HostA1:
uri="static:(ssl://HostA2:61616)" duplex=
