My Oracle Support Banner

ALSB 2.5 - Memory Leak in Weblogic.Jms.Client.Jmsproducer if Messages are Distributed to Multiple JMS Clients (Doc ID 949155.1)

Last updated on APRIL 14, 2021

Applies to:

Oracle Service Bus - Version 2.5 to 2.5 [Release Aqualogic Service Bus]
Information in this document applies to any platform.

Symptoms

MEMORY LEAK on WEBLOGIC.JMS.CLIENT.JMSPRODUCER


The problem happens with a ALSB 2.5 application that distributes messages to multiple jms clients.The
application has a jms proxy service which delivers the inbound message to different jms business services
based on the content of the message. The memory leak are observed for the objects of class
weblogic.jms.client.JMSProducer. If the inbound message is selected only for 1 jms client then
there is no leak, but if it is selected for more than one, say 'x', then the instance count for
weblogic.jms.client.JMSProducer objects also increase by x.

Changes

This issue is relevant for ALSB 2.5/WLS9.2.

Cause

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
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.