Hi John, did you look at the Message Time To Live (at the point where the reply gets sent)? >From what I've learned: The broker keeps the messages in memory until they expire. And if you ron non persistent messaging, these temp queues might not have any listener any more, but still waste memory.
Regards Herbert Von: "John Lilley" <john.lil...@redpointglobal.com.INVALID> An: "users@activemq.apache.org" <users@activemq.apache.org> Datum: 12.12.2022 17:56 Betreff: [Ext] broker memory usage for temporary queues Greetings! We are seeing that our broker is getting OOM errors with 2GB JVM size. We use a lot of temporary queues for JMS reply-to with the RPC pattern. In order to better understand what drives memory use, is there a rule of thumb for the memory we would expect to be used by each temporary queue? If we find that reply-to temporary queues are using a lot of memory and there is no easy way to tune the broker to avoid that, can you give me an idea of the time it takes to create and destroy the temporary queue and its consumer? Is there a client-side setting for garbage collecting idle queues and recreating them as needed? If it is not too slow, we may find that recreating the queue each time, or aging them out, is a good approach. Any ideas appreciated for how to reduce memory use in this design. Thanks John John Lilley Data Management Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761 | 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.
