Memory Leak Where JmsSession Holding Message Even After Being Consumed By MDB
(Doc ID 2410245.1)
Last updated on AUGUST 31, 2020
Applies to:Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
MDB is configured to consume sessions from JMS Distributed queue. Even after consuming all messages, on Heap dump we still see the last messages.
In the analysis with MAT (Eclipse Memory Analyzer Tool) it can be seen a memory leak suspect on weblogic.jms.client.JMSXASession.
In MAT, all the references remaining were related to JMSPushRequest (carryForwardOnReconnect on JMSSession). Even disabling reconnect from Connection Factory and set MessageMaximum to 1 made no difference in the behavior.
If Messages are really big in size it may become a big issue if you have Multiple MDB connecting on the same environment, thus this will end causing Out Of Memory Errors.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document