PI58664: Liberty collective member status is incorrect

Fixes are available

APAR status

Closed as program error.

Error description

Collective member status is incorrect.  Issue is caused by
.collective file not being created in the appropriate
directory
when member is joined.

Member traces show the following issue

[2/18/16 10:25:09:316 GMT+01:00] 00000025 id=

ective.repository.client.internal.RemoteConnectionHelperImpl
3
Looking for collective marker file at
[/opt/wlp/usr/servers/server1/
resources/collective/.collective]
[2/18/16 10:25:09:317 GMT+01:00] 00000025 id=

ective.repository.client.internal.RemoteRepositoryConnection
1
IOException while attempting connect to collective
controller,
this can happen if the controller is unreachable


java.net.ConnectException: Connection failed.
Client is not a member joined to this collective.

While attempting to establish a connection to the collective
controller, the connection fails as the collective member is
not able to locate the following file:
/opt/wlp/usr/servers/server2/resources/collective/.collectiv
e

Local fix

As a workaround, the customer may add the '.collective' file in
the specified locations (<memberRoot>\resources\collective).
That should enable them to see proper status (and establish
communication) with the controller.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty using collectives in 8.5.5.8 *
*                  and 8.5.5.9.                                *
****************************************************************
* PROBLEM DESCRIPTION: When upgrading Liberty collectives from *
*                      a previous version of WebSphere         *
*                      Liberty, to 8.5.5.8 or 8.5.5.9, member  *
*                      to controller connection fails to be    *
*                      established. As a result, the           *
*                      AdminCenter displays incorrect status   *
*                      of the collective members.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When upgrading existing Liberty collectives to 8.5.5.8 or
8.5.5.9, the member to controller connection fails to be
established. As a result, the AdminCenter displays incorrect
status of the
collective members when they are started.

Collective member traces show the following messages:

Looking for collective marker file
at[<WLP_HOME>/usr/servers/<serverName>/resources/collective/.col
lective]

IOException while attempting connect to collective controller,
this can happen if the controller is unreachable
java.net.ConnectException: Connection failed.

Client is not a member joined to this collective.

Problem conclusion

The code was improved to fix this issue.

The fix for this APAR is currently targeted for inclusion in fix
pack 16.0.0.2.  Please refer to the Recommended Updates page for
delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

As a work-around, you may create a '.collective' file in:
<WLP_HOME>/usr/servers/<serverName>/resources/collective/

Comments

APAR Information

APAR number
PI58664
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-03-07
Closed date
2016-05-11
Last modified date
2016-06-13

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

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

Document Information

Modified date:
04 May 2022

Tips

PI58664: Liberty collective member status is incorrect

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

R855 PSY

Document Information

Share your feedback

Need support?