PI81552: Application state becomes stale at the Liberty collective controller

Fixes are available

APAR status

Closed as program error.

Error description

If a Liberty server becomes overloaded (high CPU,
thread-pool
exhaustion, high heap usage) and can not send it's
heart-beat
to the collective controller it is marked as "down" by the
controller (CWWKX9078I: The collective member ... on host
...
with the user directory ... missed 3 heart beats. Attempting
deregistration).

The server will complete it's long running tasks (or grow
its
thread-pool enough) and will begin sending it's heartbeat to
the controller; the controller reports that the server has
rejoined the collective (CWWKX9076I: The collective member
...
on host ... with the user directory ... connected to the
collective controller).

The web server Plug-in continues to send an HTTP 503
(ws_common: ODR says reject with status code 503) to any
client
trying to access a service hosted on the previously
unavailable
server.

This problem happens because the "application state becomes
stale at the Liberty Collective Controller".

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty Network Deployment -         *
*                  collectives                                 *
****************************************************************
* PROBLEM DESCRIPTION: Performance issues on member hosts can  *
*                      cause application to be reported as     *
*                      stopped at the collective controller.   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A collective controller monitors members of the collective via
heart beats sent by the members at a set interval.  Should a
member miss sending three consecutive heart beats the controller
will mark that member and its applications as stopped and issue
message CWWKX9078I.  When a member experiences temporary
performance issues it may cause the heart beat task to be
delayed long enough to trigger the controller to mark the member
and its applications as stopped.  When the member resumes heart
beating the member server is reset to the started state but its
applications are not.

Problem conclusion

Application state is updated in the collective repository when a
member resumes heart beating.

The fix for this APAR is currently targeted for inclusion in fix
pack 17.0.0.3.  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
PI81552
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-05-12
Closed date
2017-09-14
Last modified date
2017-09-14

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
LIBERTY PROFILE
Fixed component ID
5724J0814

Applicable component levels

RCD0 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":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 May 2022

Tips

PI81552: Application state becomes stale at the Liberty collective controller

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

RCD0 PSY

Document Information

Share your feedback

Need support?