Hi Justin!  Thanks for the reply.  Let me try to round up all of the settings 
and symptoms a little more carefully.
john




[rg] <https://www.redpointglobal.com/>

John Lilley

Data Management Chief Architect, Redpoint Global Inc.

888 Worcester Street, Suite 200 Wellesley, MA 02482

M: +1 7209385761<tel:+1%207209385761> | 
john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com>
From: Justin Bertram <jbert...@apache.org>
Sent: Tuesday, December 20, 2022 2:10 PM
To: users@activemq.apache.org
Subject: Re: Recovery from broker OOM

*** [Caution] This email is from an external source. Please use caution 
responding, opening attachments or clicking embedded links. ***

Could you be more specific about the behavior you're observing?

Also, what parameters are you passing in your connection URL?

Lastly, does the broker which is running out of memory have a backup?


Justin

On Tue, Dec 20, 2022 at 2:18 PM John Lilley 
<john.lil...@redpointglobal.com.invalid<mailto:john.lil...@redpointglobal.com.invalid>>
 wrote:
Greetings,

We were recently seeing some broker OOM errors, probably due to an 
overabundance of reply-to queues.  While the broker itself seems to recover, 
our client code does not.  I suspect that we need to do something when that 
happens, or if the broker is restarted for any reason.  Is there any guidance 
for recovering from a broker restart or OOM error?  Using the vanilla JMS 
client, from our pom.xml:

<dependency>
                <groupId>org.apache.activemq</groupId>
                <artifactId>artemis-jms-client-all</artifactId>
                <version>2.26.0</version>
</dependency>

john


[rg]<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.redpointglobal.com%2f&c=E,1,Ymiu3vSK1uOSUa8Oe7KEumTXQk5USWveIzcyC4NGBQAMGFag2K9glHJDyu7h7pFVi4oqD-Euyvw-kc_nCQlpdxWxTwYa5c_9coeJwYICSWE6XX0Q&typo=1>

John Lilley

Data Management Chief Architect, Redpoint Global Inc.

888 Worcester Street, Suite 200 Wellesley, MA 02482

M: +1 7209385761<tel:+1%207209385761> | 
john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com>

PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is confidential 
and is intended solely for the use of the individual(s) to whom it is 
addressed. If you believe you received this e-mail in error, please notify the 
sender immediately, delete the e-mail from your computer and do not copy, print 
or disclose it to anyone else. If you properly received this e-mail as a 
customer, partner or vendor of Redpoint, you should maintain its contents in 
confidence subject to the terms and conditions of your agreement(s) with 
Redpoint.

PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is confidential 
and is intended solely for the use of the individual(s) to whom it is 
addressed. If you believe you received this e-mail in error, please notify the 
sender immediately, delete the e-mail from your computer and do not copy, print 
or disclose it to anyone else. If you properly received this e-mail as a 
customer, partner or vendor of Redpoint, you should maintain its contents in 
confidence subject to the terms and conditions of your agreement(s) with 
Redpoint.

Reply via email to