PM16868: WORKLOAD MANAGEMENT OUTOFMEMORY ON PROXY SERVER

Fixes are available

APAR status

Closed as program error.

Error description

In high load scenarios with the WebSphere Application Server
proxy server left running for long periods of time, there is a
slow memory leak in the work load manager (WLM) code. This is
dependent on the amount of load and may take a long time to
manifest itself. A slow memory leak in the WLM code on the
Proxy Server can eventually can an OutOfMemory condition on the
Proxy Server JVM.

Using a heap analyzer, the leak would center around the
following classes:

com.ibm.ws.cluster.channel.ChannelTargetRule
com.ibm.ws.cluster.selection.rule.RuleEtiquette
com.ibm.ws.cluster.topography.ClusterDescriptionImpl

The underlying cause is with a cache of Target objects being
held by the WLM code which may not be cleaned up properly,
eventually leading to the OOM.

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the IBM WebSphere Application      *
*                  Server V6.1 and V7.0 Proxy Server under     *
*                  high load                                   *
****************************************************************
* PROBLEM DESCRIPTION: Workload management (WLM) OutOfMemory   *
*                      (OOM) on Proxy Server                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In high load scenarios with the WebSphere proxy server left
running for long periods of time, there is a slow memory leak in
the work load manager (WLM) code. This is dependent on the
amount of load and may take a long time to manifest itself.
A slow memory leak in the WLM code on the Proxy Server can
eventually can an OOM condition on the Proxy Server JVM.

Problem conclusion

Using a heap analyzer, the leak would center around the
following classes:

com.ibm.ws.cluster.channel.ChannelTargetRule
com.ibm.ws.cluster.selection.rule.RuleEtiquette
com.ibm.ws.cluster.topography.ClusterDescriptionImpl

The underlying cause is with a cache of Target objects being
held by the WLM code which may not be cleaned up properly,
eventually leading to the OOM.  This APAR addresses the issue
by ensuring that the references within the channel target
cache are cleaned up appropriately.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.37, 7.0.0.15.  Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM16868
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-21
Closed date
2010-10-22
Last modified date
2011-04-15

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022

Tips

PM16868: WORKLOAD MANAGEMENT OUTOFMEMORY ON PROXY SERVER

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?