There is no way to completely disable large message support. This is
because clients are free to send messages larger than the configured
journal-buffer-size (490KB by default). When that happens the broker has no
choice but to treat the message as "large" and stream it to disk rather
than storing
How is your cluster-connection configured? Are you using broadcast &
discovery groups? If so, I've seen instances of this when stopping and
starting the broker quickly. As far as I can tell the UDP multicast
datagram somehow is delivered back to the broker that sent it originally.
As long as your
Hi,
we have upgraded some of our environments from 2.28 to 2.30, others from 2.24
to 2.30 and all upgraded instances now show this strange log message during
live node restart cycle:
There is a possible split brain on nodeID 165c6eec-0429-11ed-a12a-42010a961402.
Topology update ignored
Full r
