Ok, it just happened again. How to generate heap dump?
Rahman Gunawan SITSS Software Developer NASA SEWP / SITSS HALVIK Corporation 7601 Ora Glen Dr, Greenbelt, MD 20770 C: 240.444.6003 O: 301.614.5257 [email protected] -----Original Message----- From: Justin Bertram <[email protected]> Sent: Thursday, November 13, 2025 12:25 PM To: [email protected] Subject: [EXTERNAL] [BULK] Re: Memory leak? CAUTION: This email originated from outside of NASA. Please take care when clicking links or opening attachments. Use the "Report Message" button to report suspicious messages to the NASA SOC. Any update here, Rahman? Justin On Mon, Nov 10, 2025 at 8:13 AM Justin Bertram <[email protected]> wrote: > I think it's unlikely for there to be a memory leak in the JGroups > configuration used by Artemis. It's more likely that this > OutOfMemoryError is a symptom of a separate issue in the same JVM. > However, we need more data to determine what really happened. Did you > acquire a heap dump when this happened (e.g. via > -XX:+HeapDumpOnOutOfMemoryError)? If so, could you upload somewhere and post > the link here for analysis? > > Also, can you elaborate on your use-case and describe the > circumstances surrounding when this happened? > > > Justin > > On Mon, Nov 10, 2025 at 7:34 AM Gunawan, Rahman (GSFC-SEWP)[Halvik > Corp] <[email protected]> wrote: > >> I’m using Artemis 2.42.0, is there a memory leak in artemis jgroup >> configuration? Got error: >> >> 2025-11-10 07:15:13,964 ERROR [org.jgroups.util.TimeScheduler3] >> JGRP000212: failed submitting task to thread pool >> >> java.lang.OutOfMemoryError: Java heap space >> >> failed handling incoming message >> >> java.lang.OutOfMemoryError: Java heap space >> >> >> >> *Rahman Gunawan* >> >> *SITSS Software Developer* >> >> NASA SEWP / SITSS >> >> HALV*I*K Corporation >> >> 7601 Ora Glen Dr, Greenbelt, MD 20770 >> >> C: 240.444.6003 >> O: 301.614.5257 >> >> [email protected] >> >> >> >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
