OK. The client app has a durable consumer C has connected to Topic T, and
while it is active, messages X, Y, and Z are eventually delivered by the
broker and consumed by C. Then, C disconnects and then reconnects
(sometimes immediately). When C reconnects, sometimes messages X, Y, and Z
are
Hello everyone,
I am having two brokers which run under JDBC Master-Slave using MySQL as
database.
For some reasons, I had to turn the JDBC Master-Slave off by adding config
useDatabaseLock="false" to activemq.xml:
Now, both brokers become active on same database.
However, I found a topic which
There's no mechanism to request that the broker send you everything it has;
if that is going to happen, it happens when the client connects.
In your testing, are you saying that if topic T has messages A, B, and C
that have not yet been consumed by offline durable consumer C1, and
consumer C2
Can you try creating each broker in a different thread in your tests? The
issue I think is that in the SslContext class the ThreadLocal variable is
static so it is going to be shared and interfere when you try to configure
2 brokers in the same JVM and the same thread is creating transports.
