We don't explicitly test cross-version compatibility so we can't make any
guarantees, but we try not to do anything that would break compatibility
and I haven't heard of any cases where anyone has found an incompatibility.
But as always, test in a non-operational environment before you do it live.
It sounds like an issue on retrofit. Not something that we would be able to
help. Unless you point us to a specific but we have.
Try tweaking classparh. Adding libraries you are missing. Quite a
possibility actually.
On Fri, Sep 15, 2017 at 9:35 PM Justin Bertram wrote:
> Do you have a repr
Do you have a reproducible test-case you could share?
Justin
On Wed, Sep 13, 2017 at 8:25 AM, aragoubi wrote:
> I have a mqtt interceptor inside my artemis broker.
> The jar of the interceptor contains a list of classes used basically for
> creating web services calls.
> I am using Retrofit li
I'm running ActiveMQ 5.10.0 with an embedded camel route. It's been running
fine until we connected the master to an instance 5.14.5.
5.10.0 Network Connector:
I'm using ActiveMQ-5.5.1 in a star topology configuration - many leaf brokers
are feeding one centralized broker. I would like to start with the hub in
the middle and update it to ActiveMQ-5.15.0, but I don't know if the
Transport layers (and NetworkBridges) are compatible. Does anyone know if
th
When a message is stuck on a given queue, have you confirmed that there is
at least one consumer for that queue connected to the broker on which the
message resides? A JMX viewer such as JConsole is ideal for determining
this.
I haven't used the rebalanceClusterClients option before, but I expect
