PK82259: ADD IBM PROPRIETARY JVM OPTION -XMAXT0.5 TO NODEAGENT START PROGRAM.

Fixes are available

APAR status

Closed as program error.

Error description

Without the option, the nodeagent V7 footprint measures 288.5MB,
which is 6% larger than v6.1.0.9, short of the footprint goal.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: Nodeagent requires an IBM specific      *
*                      JVM option.                             *
*                      IPC needs to close cleanly at server    *
*                      shutdown                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Nodeagent requires an IBM specific JVM option to limit the
memory footprint to an acceptable level.

Inter-Process Communications (IPC) connector needs to close
cleanly at server shutdown. When a server is shutting down,
the IPC connector server is also brought down. However, there
may be outstanding incoming IPC request. On certain operating
systems (for example, iSeries/IBMi) such requests do not
automatically get ignored, and they may trigger a
NullPointerException in the IPC code.

Problem conclusion

Nodeagent requires an IBM specific JVM option to limit the
memory footprint to an acceptable level. The solution has been
worked out as follows. LaunchCommand is a utility class used by
server launchers. In this class we test whether the server
type is nodeagent, and whether the JDK in use is IBM provided.
If both tests pass, we add the required IBM JVM option to the
list of parameters used to start the server process.


IPC needs to close cleanly at server shutdown. When a server is
shutting down, the IPC connector server is also brought down.
However, there may be outstanding incoming IPC requests. On
certain operating systems (such as IBMi/iSeries) such requests
do not automatically get ignored, and they may trigger a
NullPointerException in the IPC code. The fix is, when a server
starts to shut down, we do not immediately let the IPC
connector tear down, but rather clean up any possible
outstanding incoming requests first. Only then do we let the
IPC connector tear down procedure begin.

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
PK82259
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-10
Closed date
2009-06-09
Last modified date
2009-06-09

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

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

PK82259: ADD IBM PROPRIETARY JVM OPTION -XMAXT0.5 TO NODEAGENT START PROGRAM.

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?