Hello team,
There was a mistake with the previous
email(https://lists.apache.org/thread/6to6lt69vxvp3sbslr8xob24p61bb6ow ),
please refer to this one.
My activeMQ cluster running on master-slave mode.Two nodes try aquiring
mysql lock to become master.I upgrade the MySQL from 5.7 to 8.0，and
Hello team,
My activeMQ cluster running on master-slave mode.Two nodes try aquiring
mysql lock to become master.I upgrade the MySQL from 5.7 to 8.0，and noticed
that it will crash every 4-5 days.It will goes will shortly after i restart the
service.
The error log is like:
It seems that th
Managed to solve this. It was actually relating to how one of the initial
messages was added to the queue. It's submitted to another queue and is
processed by an external system.
The point is, when I submit it to the input queue, when it's processed, a
message is added to "status" and then th
Thanks actually!
That may just be good enough.
Was trending that way (6.x client to 5.18broker) anyway. Just trying to
see if there is anything I missed.
Good to know the wire protocol didn't change between 5x and 6x.. BTW -- I
assume you mean OpenWire -- which is all I use OpenWire/TLS.
Yes, this is all referring to OpenWire (which is the only protocol impacted by
the Jakarta API changes.)
Matt Pavlovich-
> On Dec 10, 2024, at 10:15 AM, Fred Welland wrote:
>
> Thanks actually!
>
> That may just be good enough.
>
> Was trending that way (6.x client to 5.18broker) anyway. J
Fred-
There isn’t going to be anything more “official” from the open source project.
If you require more official certification, then you should look at vendor
support options.
The cross broker-client version compatibility has some unit tests and
interactive testing was completed. The key piec
Yeah I know -- tested that a few ways (and mentioned that in my post).
But is it endorsed or recommended (by any authoritative source)?
I've scrapped around and seen a comment or two that says stuff like -- "
yeah it (new client to older remote broker) may work -- but that really
isn't tested or
Hi Fred-
The 6.x client jar can work with to 5.x brokers.
Matt Pavlovich
> On Dec 10, 2024, at 8:56 AM, Fred Welland wrote:
>
> Subject summarizes my question: I can not seem to find an RAR artifact
> that is 'ok' for a remote AMQ broker 5.17x/5.18x but is suitable for
> Jakarta based applic
Subject summarizes my question: I can not seem to find an RAR artifact
that is 'ok' for a remote AMQ broker 5.17x/5.18x but is suitable for
Jakarta based application platforms like Wildfly 26x and greater.
Does one exist? (Or is there a recipe to provide a workable solution?)
This GAV: 'o
