PI75433: Liberty collective member status becomes stale at the controller.

Fixes are available

APAR status

Closed as program error.

Error description

This situation can occur when a collective has multiple
controllers but a member is only configured to know about a
subset of the controllers.  When the controllers known to
the member are stopped, the member will be unable to connect
to any controller.  The remaining running controllers, the
ones unknown to the member, will no longer see updates to
the member's status.  For example, say a collective has
three controllers and a member is configured to know only of
controller one.  If controller one is stopped and controller
two is used to stop the member, the member's state is
changed to "stopping" and remains in that state.

Note that it is a best practice to configure collective
members with all of the controllers in a collective.  This
is done with the collectiveMember configuration element.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty - Systems Management         *
*                  Functions                                   *
****************************************************************
* PROBLEM DESCRIPTION: Liberty collective member status        *
*                      becomes stale at the controller.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This situation can occur when a collective has multiple
controllers but a member is only configured to know about a
subset of the controllers.  When the controllers known to the
member are stopped, the member will be unable to connect to any
controller.  The remaining running controllers, the ones unknown
to the member, will no longer see updates to the member's
status.  For example, say a collective has three controllers and
a member is configured to know of only controller one.  If
controller one is stopped and controller two is used to stop the
member, the member's state is changed to "stopping" and remains
in that state.

Note that it is a best practice to configure collective members
with all of the controllers in a collective.  This is done with
the collectiveMember configuration element.

Problem conclusion

The controller monitoring service was fixed to correctly
disposition the status of the member.

The fix for this APAR is currently targeted for inclusion in fix
pack 17.0.0.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
PI75433
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-01-24
Closed date
2017-01-31
Last modified date
2017-01-31

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:
04 May 2022

Tips

PI75433: Liberty collective member status becomes stale at the 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?