This sounds extremely similar to
https://issues.apache.org/jira/browse/AMQ-6877; are you the submitter of
that issue (using a different name) or in some way related? The root cause
appears to be https://issues.apache.org/jira/browse/AMQ-6823, which was
fixed in 5.15.1 and 5.16.0, so it sounds like
I spent a little time this evening going through the JDBC persistence code,
and I see no code that is specific to MariaDB and no code that appears to
handle database connection failures by seamlessly failing over to a slave
node. So if your question is simply "is there a feature to allow seamless
f
Can you work up a reproducible test-case (e.g. based on one of the
clustered examples shipped with Apache ActiveMQ Artemis) and push it to
GitHub? That would be much simpler to investigate than a bunch of cut and
pasted code and xml.
Justin
On Sat, Dec 30, 2017 at 4:02 AM, ren0909 wrote:
> I t
I tried:
1) 1 connection factories HA, one producer, two consumer.receive, all the
same queue.
2) 2 connection factories HA, one producer, two consumer.receive, all the
same queue.
3) 2 connection factories with direct tcp connection, one producer, two
consumer.receive, all the same queue.
i produ
i have this, one producer, two consumers, all same queue.
sometimes consumer0 and consumer1 DO able to receive messages consecutively,
but most of the time only consumer0 receive half of the message,
consumer1 always receive null value.
why is this the case, or if there is any setting is wrong.
(o
testing
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
