AM
To: users@activemq.apache.org
Subject: Re: Queue load resulting OutOfMemory exception
[You don't often get email from rakesh.ath...@planonsoftware.com.invalid. Learn
why this is important at https://aka.ms/LearnAboutSenderIdentification ]
Hi,
Could you please share JIRA number or pull re
From: Clebert Suconic
Sent: Monday, May 13, 2024 6:04 AM
To: users@activemq.apache.org
Subject: Re: Queue load resulting OutOfMemory exception
[You don't often get email from clebert.suco...@gmail.com. Learn why this is
important at https://aka.ms/LearnAboutSenderIdentification ]
on
on more recent versions of Artemis, I have improved paging with JDBC.
I would suggest you keep more data on paging by setting an
address-setting#max-size-bytes. However Wildfly is a few versions
behind.
Perhaps you could use Artemis standalone and consume remote from
Wildfly. Artemis is on a faste
At the moment there is no broker-specific configuration that would impact
this use-case. I recommend you simply give the JVM more memory to deal with
the size of the JDBC ResultSet.
Justin
On Thu, May 9, 2024 at 3:55 AM Rakesh Athuru
wrote:
> Hi,
>
> I am using JBoss Wildfly server with Active
Hi,
I am using JBoss Wildfly server with ActiveMQ (Artemis) configured.
I have a queue with persistency (to MS SQLServer DB) enabled, and when the
queue contains lot of messages (persisted to DB), upon restart of the Wildfly
server, queue loading results OutOfMemory error.
When I looked at heapd
