My Oracle Support Banner

Heap Memory is not Being Released by the Object "Weblogic.cluster.replication.WroManager", after the Load Test (Doc ID 2670336.1)

Last updated on MAY 18, 2020

Applies to:

Oracle WebLogic Server - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

Noticing the high memory consumption on the object "weblogic.cluster.replication.WroManager", which was not releasing memory after load test.

The environment was having 6 servers in a Cluster. Also using a custom Java Application with the default "in-memory" for HTTP session replication. Noticed that during the load testing, after 2 hours the server OS runs out of memory (OOM). Upon taking a heap dump, noticed that the memory allocation on the heap is due to the object "weblogic.cluster.replication.WroManager" which was consuming most of the memory. The memory did not get released even after the load testing concluded.

That memory was not released until the restart of the managed servers.

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
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.