IBM Support

PI58664: Liberty collective member status is incorrect

Fixes are available

16.0.0.2: WebSphere Application Server Liberty 16.0.0.2
16.0.0.3: WebSphere Application Server Liberty 16.0.0.3
16.0.0.4: WebSphere Application Server Liberty 16.0.0.4
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12

Subscribe

You can track all active APARs for this component.

 

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

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":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 October 2021