Hi!
Update...
It looks like that the issues is connected to "JMSCorrelationID", if I use a
custom property, it's works like a charm. Too bad this is the property for
identify request-response message pairs.
I created another client, just to be sure... I have very similar results, but I
ruled
Erwin,
Thank you for the feedback!
That was my first guess as well, and yes, the files are there in the directory
on "consumer side" and the directory modification date changed on "producer
side".
Unfortunatelly nothing change if I set up the minLargeMessageSize parameter in
the connector
Peter,
I suspect that the "large-message" mechanism interferes somehow.
https://activemq.apache.org/components/artemis/documentation/latest/large-messages.html
That mechanism has a default size limit in the same range.
Just as you, I found that there was an exact payload size from where the
