PK84543: MEMORY LEAK IN WEB SERVICES HANDLER POOL.

Fixes are available

APAR status

Closed as program error.

Error description

Memory leak in web services handler pool.

Heapdump shows following handler pool references growing.
.
255,395,612 (76%) [8] 2
com/ibm/ws/webservices/engine/handlers/jaxrpc/WASHandlerPool
0xffffffffe8d0fdd8
 255,395,604 (76%) [37] 2 com/ibm/ejs/csi/PoolImplThreadSafe
0xffffffffe8d0fe08
  255,395,507 (76%) [20] 2 com/ibm/ejs/csi/PoolManagerImpl
0xffffffffd52ab5b8
   255,376,255 (76%) [16] 1 java/util/Vector 0xffffffffd52ce2b8
    255,376,239 (76%) [20,480] 4,808 [Ljava/lang/Object;
0xffffffffe03d6088
     357,523 (0%) [37] 2 com/ibm/ejs/csi/PoolImplThreadSafe
0xffffffffe7c62118
     357,287 (0%) [37] 2 com/ibm/ejs/csi/PoolImplThreadSafe
0xffffffffe1ba3c00
     357,287 (0%) [37] 2 com/ibm/ejs/csi/PoolImplThreadSafe
0xffffffffd68eb3a0

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server users  *
*                  of JAX-RPC                                  *
****************************************************************
* PROBLEM DESCRIPTION: An OutOfMemoryError may occur if        *
*                      using a large number of different       *
*                      JAX-RPC web services                    *
****************************************************************
* RECOMMENDATION:  Apply a Fix Pack which contains this APAR.  *
****************************************************************
The JAX-RPC runtime maintains a pool of active handler objects
for each web service.

If a large number of different web services are used, the
number of pools may increase.  The large number of pools
could contribute to an OutOfMemoryError error.

Here is an example heapdump indicating that there are
20,480 different pools:

Heapdump shows following handler pool references growing.
.
255,395,612 (76%) [8] 2
com/ibm/ws/webservices/engine/handlers/jaxrpc/WASHandlerPool
0xffffffffe8d0fdd8
255,395,604 (76%) [37] 2 com/ibm/ejs/csi/PoolImplThreadSafe
0xffffffffe8d0fe08
255,395,507 (76%) [20] 2 com/ibm/ejs/csi/PoolManagerImpl
0xffffffffd52ab5b8
255,376,255 (76%) [16] 1 java/util/Vector 0xffffffffd52ce2b8
255,376,239 (76%) [20,480] 4,808 [Ljava/lang/Object;
0xffffffffe03d6088
357,523 (0%) [37] 2 com/ibm/ejs/csi/PoolImplThreadSafe
0xffffffffe7c62118
357,287 (0%) [37] 2 com/ibm/ejs/csi/PoolImplThreadSafe
0xffffffffe1ba3c00
357,287 (0%) [37] 2 com/ibm/ejs/csi/PoolImplThreadSafe
0xffffffffd68eb3a0

The JAX-RPC runtime is properly managing the handler objects
within each pool.  However the JAX-RPC runtime is not properly
managing the number of pools.

Problem conclusion

The JAX-RPC runtime establishes a new handler pool for each web
service.  The number of pools can increase in size and
contribute to a OutOfMemoryError.

The JAX-RPC runtime is changed to intermittently remove pools
when a large number of pools is detected.  The JAX-RPC runtime
is also changed to detect a removed pool and create a new one
if needed.   The combination of these changes will prevent the
OutOfMemoryError from occurring.

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

Temporary fix

```
ZE Fix Error, see PM06800   2010/02/22
```

Comments

APAR Information

APAR number
PK84543
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
60S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-10
Closed date
2009-05-13
Last modified date
2010-02-22

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 APP S
Fixed component ID
5724J0800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK84543: MEMORY LEAK IN WEB SERVICES HANDLER POOL.

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?