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 printing this error at each iteration:
2023-08-23 11:07:18 org.apache.camel.RuntimeCamelException: Failed to extract
body due to: javax.jms.MessageNotWriteableException: Message properties are
read-only. Message: JmsBytesMessage {
org.apache.qpid.jms.provider.amqp.message.AmqpJmsBytesMessageFacade@39dd152c<mailto:org.apache.qpid.jms.provider.amqp.message.AmqpJmsBytesMessageFacade@39dd152c>
}
2023-08-23 11:07:18 at
org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsBinding.java:174)
2023-08-23 11:07:18 at
org.apache.camel.component.jms.JmsMessage.createBody(JmsMessage.java:234)
Switching to core the messages over 100k were handled but no way to change the
minimum large messages default value.
From the support I got from Camel mailing list there is no other way than using
Camel-jms to have full large messages support:
“I am afraid that in order to use minLargeMessageSize you need to use
*camel-jms* component and *artemis-jms-client* as jms implementation,
because camel-amqp uses *qpid-jms-client.*If you have some time, you can
take a look to camel-jms”
This force us to use the Artemis connection factory
(org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory), in our
clients, to connect to the broker, decreasing the generality we like to have on
our opensource project.
I’m still testing a working configuration with Camel-jms but I was just
wondering if there was a way to disable the large messages support.
Riccardo
From: Justin Bertram <jbert...@apache.org>
Date: Friday, 1 September 2023 at 20:56
To: users@activemq.apache.org <users@activemq.apache.org>
Subject: Re: Disable large messages support at all
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 it in the journal. You can increase the journal-buffer-size to
make large messages less likely or even effectively eliminate them
depending on your use-case, but using the larger buffer may have an impact
on performance.
What "difficulties" are you having currently with AMQP, MQTT, & large
messages?
Justin
On Wed, Aug 30, 2023 at 2:21 AM Modanese, Riccardo
<riccardo.modan...@eurotech.com.invalid> wrote:
> Hello to everyone,
>
> I’m trying to configure my Camel routes (3.11) with Artemis (2.28.0)
> large messages but I’m still experiencing some difficulties.
> My clients are MQTT and my Camel routes are using AMQP endpoint.
> Is there a way to completely disable large message support on Artemis or
> to set the min value globally on Artemis to override any setting made on
> connectors bases?
>
> Regards,
>
> Riccardo Modanese
>
>
