The image indicates there's accumulation related to JSON parsing which I wouldn't expect during the normal process of consuming a message.
Can you share any more details about your use-case? Do you have a reproducer? Are the client and the broker in the same JVM? Justin On Tue, Oct 7, 2025 at 10:53 AM Thorsten Meinl <[email protected]> wrote: > Bummer. I hope this works: > > https://drive.google.com/file/d/1U7wLYGDibiJi08_egHLnRxeEcDPSZgT9/view?usp=sharing > > Am Dienstag, dem 07.10.2025 um 10:47 -0500 schrieb Justin Bertram: > > I believe your attachment was stripped by the mailing list. Could you > > provide a link to it? > > > > > > Justin > > > > On Tue, Oct 7, 2025 at 10:38 AM Thorsten Meinl > > <[email protected]> > > wrote: > > > > > Hi, > > > > > > We are using the Artemis JMS client 2.42.0 in an application with > > > the > > > following pattern: > > > > > > try (var context = > > > connectionFactory.createContext(Session.SESSION_TRANSACTED); > > > var consumer = context.createSharedDurableConsumer(topic, > > > queueName, QUEUE_FILTER)) { > > > while (!Thread.currentThread().isInterrupted()) { > > > var message = consumer.receive(); > > > if (message == null) { > > > break; > > > } > > > // do some stuff > > > context.commit(); > > > } > > > } > > > > > > The service regularly runs out of memory after some time. We > > > created a > > > heap dump and found some data structures deep in the Artemis client > > > of > > > more than 500MB while our messages are are in almost all cases > > > below > > > 1MB in some exceptional cases up to 20MB. I have attached a snippet > > > of > > > the heap dump. > > > Is this an issue in the client code or are we doing something wrong > > > in > > > our application code? > > > > > > Thanks, > > > > > > Thorsten > > > > > > > > > -- > > > Dr.-Ing. Thorsten Meinl > > > KNIME AG > > > Talacker 50 > > > 8001 Zurich, Switzerland > > > > > > > > > > > > ------------------------------------------------------------------- > > > -- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > For further information, visit: https://activemq.apache.org/contact > > > > > -- > Dr.-Ing. Thorsten Meinl > KNIME AG > Talacker 50 > 8001 Zurich, Switzerland > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact > > >
