As I understand it, the clientId parameter isn't a selector; rather, it
ensures that your consumer gets messages consistent with what has already
been delivered to it even if the session has expired, but it is not meant
to specify that you only consume messages produced by yourself. So the
delivery
I expect that if you could find a Node library that implemented one of
those other protocols, you'd be able to interact with the broker, but I
can't say for certain since I've never used any of the non-OpenWire
protocols under any language, let alone Node.
Did you already do a Google search for No
1) Those JARs should all be compatible with one another, since they're all
packaged as part of the ActiveMQ installation bundle. I was trying to see
if maybe you'd added your own Spring JARs to the classpath in addition to
the ones from ActiveMQ's lib directory, but that's clearly not the case,
and
> after all three start, only journal replication is only seen on one of the
> slaves, i.e., the "active" slave.
That's expected.
> when the original master is restarted, the first "active" slave (the current
> master) will stay as the live broker even with "allow-failback" set to true
That's
I have a master slave non-colocation set up of one master and two slaves.
1. after all three start, only journal replication is only seen on one of
the slaves, i.e., the "active" slave.
2. try to simulate the failover scenarios.
scenario A:
- when the master is killed, the "active" slave comes up
Background
--
I am studying ApacheMQ for a project where we need a message broker. Upon
reading the [official page][1] I see some features that I am interested in:
- Access to messaging [Enterprise Integration Patterns][2] (EIPs)
- Support for the [STOMP][3], [AMQP][4], [MQTT][5] and [O
Thanks Tim!
(1)
I made sure if my activemq loaded Spring-related JARs by booting activemq
with -verbose:class option.
There seem to be several Spring-related JARs as follows.
/opt/apache-activemq/lib/activemq-spring-5.14.3.jar
/opt/apache-activemq/lib/optional/spring-beans-4.1.9.RELEASE.jar
/opt/
