ocessing, however in this case
> > it's not clear why the message has been discarded, which makes intercepting
> > such errors very hard.
> >
> >
> > From: Robbie Gemmell
> > Date: Monday, 4 September 2023 at 19:08
> > To: users@activemq.apa
t processing, however in this case
> it's not clear why the message has been discarded, which makes intercepting
> such errors very hard.
>
>
> From: Robbie Gemmell
> Date: Monday, 4 September 2023 at 19:08
> To: users@activemq.apache.org
> Subject: Re: Disable large mes
obbie Gemmell
Date: Monday, 4 September 2023 at 19:08
To: users@activemq.apache.org
Subject: Re: Disable large messages support at all
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 b
mqp doesn’t support the minLargeMessage
> (though in my tests I was able to get the stream from Artemis once I switched
> to use core instead of amqp)
>
> I’m looking forward to see the minLargeMessage supported by Camel streams
> also with amqp endpoint.
>
> From: Robbie Gemme
rd to see the minLargeMessage supported by Camel streams also
with amqp endpoint.
From: Robbie Gemmell
Date: Monday, 4 September 2023 at 14:11
To: users@activemq.apache.org
Subject: Re: Disable large messages support at all
Though actually, another thing occurred to me...you said your "client
> > 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 o
; 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
> Date: Friday, 1 September 2023 at 20:56
> To: users@activem
Justin Bertram
Date: Friday, 1 September 2023 at 20:56
To: 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 (49
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
