Hi Justin,
Thank you for your reply.
I had no way to get large messages support using Camel routes with Camel-amqp
endpoint.
With Camel-amqp, using qpid connection
(org.apache.qpid.jms.JmsConnectionFactory), messages over the default 100kb
weren’t processed.
Camel went to an infinite loop pr
The Artemis broker / client handling of 'large' messages, and
'streaming payload to/from file at client' are 2 separate things and
shouldnt be conflated.
The Artemis 'Core' JMS client + broker consider messages over 100kb by
default 'large' and treat them a little differently in terms of how
they
Though actually, another thing occurred to me...you said your "clients
are MQTT", in which case the Artemis client minLargeMessageSize config
and broker side amqpMinLargeMessageSize config wont necessarily be in
play if your Camel bits are only consuming messages, as those configs
primarily affect
I was just wondering if there was a way to disable, or at least force globally
from server side, a value for that parameter.
I mean, the default value is in some way enforced by the broker if no override
is done. So, in the same way, I was wondering if this default parameter could
be changed wit
Neither the client-side minLargeMessage or broker-side
amqpMinLargeMessage config will have much effect if you are only
consuming from camel / JMS client, since as before they mainly
influence publishing. The Artemis JMS client sends messages 'large'
slightly differently, doing this when its minLar
