M: +1 7209385761 |
john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com>
From: Justin Bertram
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
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
wrote:
> Greetings,
>
>
>
> We were recently
;
From: Paul Gale
Sent: Tuesday, December 20, 2022 1:54 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. ***
What OS are you using?
On Tue, Dec 2
What OS are you using?
On Tue, Dec 20, 2022 at 3:18 PM John Lilley
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
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
