PK82446: OCCASIONAL OUT OF MEMORY ERROR WHEN RUNNING WS-N AND WS-RM WITH MULTIPLE MESSAGES

Fixes are available

APAR status

Closed as program error.

Error description

An "out of memory" exception occurs on WebSphere Application
Server Distributed when running the following scenario:

- Two single server machine setup

- One machine contains a WS-N producer, subscriber, and consumer
  application.

- The other machine contains a WS-N broker.

- A WS-RM managed persistent policy set is applied throughout
 (using a filestore, a 768Mb heap on the JVM, and without
 in-order applied)

- There are 300 consumers (each with unique endpoints) which
  are subscribed to the broker.

- A single message is then published to the broker every
  30 seconds, and the consumers are checked regularly to
  ensure that the message is delivered fro the broker to all
  300 consumers.

This scenario works fine for around 200 publishes but then
fails with the exception on the broker application server
and a series of generated heapdumps. The application server
then crashes.

Here is a snippet of the exception:
[2/3/09 18:28:21:326 GMT] 00000004 HAGroupImpl   I
HMGR0132I: The local member  of group
WSAF_SIB_BUS=notificationBus, WSAF_SIB_MESSAGING_ENGINE =
p5weft30.server1-notificationBus, type=WSAF_SIB failed to
respond properly to a health check. The exception is
java.lang.OutOfMemoryError
 at java.lang.Class.getMethodImpl (Native Method)
 at java.lang.Class.getMethod (Class.java:823)
 at com.ibm.ws. sib.utils.ras.SibTr.push (SibTr.java:442)
 at com.ibm.ws.
sib.admin.impl.HAManagerMessagingEngineImpl.isAlive
(HAManagerMessagingEngineImpl.java:299)
 at com.ibm.ws. hamanager.impl.HAGroupImpl.doIsAlive
(HAGroupImpl.java:829)
 at com.ibm.ws.
hamanager.impl.HAGroupImpl$HAGroupUserCallback.doCallback
(HAGroupImpl.java:1331)
 at com.ibm.ws. hamanager.impl.Worker.run (Worker.java:64)
 at com.ibm.ws. util.ThreadPool$Worker.run
(ThreadPool.java:1527)
. The JVM will be terminated.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server V7.0   *
*                  users of JAX-WS dynamic ports,              *
*                  WS-Notification or WS-ReliableMessaging     *
****************************************************************
* PROBLEM DESCRIPTION: An OutOfMemoryError may occur when      *
*                      using WS-Notification,                  *
*                      WS-ReliableMessaging, or applications   *
*                      using JAX-WS dynamic ports              *
****************************************************************
* RECOMMENDATION:  Install a fixpack that contains this APAR   *
****************************************************************
An OutOfMemoryError may occur while using JAX-WS dynamic ports.
Dynamic ports are ports that do not exist in the WSDL and are
added using the Service.addPort(...) method.  Users of
WS-Notification and WS-ReliableMessaging, which exploit JAX-WS
dynamic ports, may also be affected.

Problem conclusion

The OutOfMemoryError is the result of JAX-WS Service
instances not being correctly cleaned up when they go out of
scope in the client application program.  When the Service
instance is no longer referenced in the client application, it
should be released (via the Java Virtual Machine Garbage
Collection mechanism).  This was not happening.  Over time,
this can result in an OutOfMemoryError condition.

The fix allows a Service instance to be correctly released
when it is no longer referenced by the client application.
The resources related to the dynamic ports under that service
are also correctly released.  This will prevent the
OutOfMemoryError condition.

The fix for this APAR is currently targeted for inclusion in
fix pack 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

Comments

APAR Information

APAR number
PK82446
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-12
Closed date
2009-04-14
Last modified date
2009-09-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 APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK82446: OCCASIONAL OUT OF MEMORY ERROR WHEN RUNNING WS-N AND WS-RM WITH MULTIPLE MESSAGES

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

Document Information

Share your feedback

Need support?