The most interesting thing is that this error is only on production,
and when I try to reproduce it locally, I don’t have an error on the
broker, but still the message is considered large, although I set the
connectionFactory.setMinLargeMessageSize(9) parameter and see
in debug mode what is
The stack trace indicates that the broker is receiving a
SESS_SEND_CONTINUATION packet from a client. This kind of packet is only
sent when a core client is sending a large message. However, based on the
information you have provided the client doesn't appear to be sending a
large message. I can on
