PI35265: ECSA STORAGE GROWTH WHEN RESOURCE MANAGERS (RESMGR) ARE NOT DELETED

Fixes are available

APAR status

Closed as program error.

Error description

There are some paths, where resource managers (RESMGR) for
Local Communication (LCOM) are not being deleted.  This leads
to an ECSA storage growth with RME eyecatchers.
If recovery is entered (like if a cancel is done), this can
cause all these resource mangers (1000's of them), to all run
at the same time.  Since they're running at the same time, it
caused a growth in WAS CPOOLs to process them.  WAS processed
the CELLs and are released, but once the the CPOOLs are
expanded, they are are not contracted.  Leading to another
storage growth in ECSA.  These CPOOLs are BBO SRB parm Cpool2
(with BBOOSRBP eyecatcher) and SRBF Dynamic Area Cpool (which
does not have an eyecatcher).

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0, V8.0, and V8.5                 *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere Application server for z/OS   *
*                      Local Communication may cause ECSA      *
*                      growth.                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
End of Memory resource managers are established during a Local
Communication (LCOM) Connect request.  Its possible that these
RESMGRs are not deleted when the Connection is closed by the
client-side of the connection.  The client-side may be a server
initiating the connection (such as a NodeAgent to a local
AppServer) or a raw client (such as dumpNameSpace.sh).
If the client address space establishes a large amount of LCOM
Connections over time, then a large amount of RESMGRs could
be established between the the Client and the AppServer.  If
the AppServer is terminated in this scenario, then RESMGRs are
all driven at the same time.   The RESMGR exit that is driven
will obtain CPOOL cells from 2 WebSphere CPOOLs.  This flood
of activity causes the 2 WebSphere CPOOLs involved in this
flow to expand.
The 2 CPOOLs described above are obtained in key 2 from
subpool 241.   They are: SCBBO SRB parm Cpool2
(with BBOOSRBP eyecatcher) and SRBF Dynamic Area Cpool (which
does not have an eyecatcher).

Problem conclusion

Local communication code has been modified to delete the
RESMGRs that are established during the Connection when the
Connection is closed.

APAR PI35265 is currently targeted for inclusion in Fix Packs
7.0.0.39, 8.0.0.11, and 8.5.5.6 of WebSphere Application Server.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

In addition, please refer to URL:
http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack PTF information.

Temporary fix

Comments

APAR Information

APAR number
PI35265
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-02-18
Closed date
2015-03-05
Last modified date
2015-11-04

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
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UI32147
UP15/10/31 P F510

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI35265: ECSA STORAGE GROWTH WHEN RESOURCE MANAGERS (RESMGR) ARE NOT DELETED

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

R700 PSY UI32147

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?