PM89824: NODEAGENT MIGHT NOT RESTART APPSERVER IF THE LOG

Fixes are available

APAR status

Closed as program error.

Error description

On a node where the WebSphere variable LOG_ROOT has been
customized, application server JVMs that fail might not be
automatically restarted by the nodeagent.

Local fix

Configuring websphere variables so the nodeagent and appserver
see the same value of $log_root.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Network Deployment edition or Admin  *
*                  Agent with monitoring policies set to       *
*                  automatically restart failed appserver      *
*                  JVMs.                                       *
****************************************************************
* PROBLEM DESCRIPTION: After customizing WebSphere variable    *
*                      LOG_ROOT, automatic restart of          *
*                      failed appserver JVMs might not occur.  *
****************************************************************
* RECOMMENDATION:  Install a fix pack containing this APAR.    *
****************************************************************
Automatic restart of appserver JVMs is handled by the
node agent or admin agent JVM process.
Normally this process and appserver processes see the same
value of the  WebSphere environment variable LOG_ROOT, however
it can be customized so they are different.
When a node agent or admin agent detects that a server has
stopped responding, in some cases it looks for that server's
PID file to see if the server was stopped deliberately (and
the PID file has been removed), or unexpectedly (and the PID
file is still present.)
If an appserver stopped unexpectedly, and its monitoring
policy is set to automatically restart it, the agent will
restart it.
In some cases where the WebSphere variable LOG_ROOT differed
between agent and appserver, the agent could look in
the wrong location for the appserver PID file and not find it,
and then conclude that a normal shutdown had occured, which
was incorrect.   This would result in a failed JVM not being
restarted.

Problem conclusion

The code is changed to use the LOG_ROOT variable at the scope
of each appserver instead of the variable at the scope of the
agent.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.31, 8.0.0.8, and  8.5.5.1.  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
PM89824
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-05-27
Closed date
2013-07-19
Last modified date
2013-07-19

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
R800 PSY
UP
R850 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":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 January 2022

Tips

PM89824: NODEAGENT MIGHT NOT RESTART APPSERVER IF THE LOG_ROOT ENVIRONMENT VARIABLE IS CHANGED

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?