IBM Support

PH41840: Cannot get a WOLA connection for a client after Configuration update

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • There is a timing window during the WOLA Channel shutdown
    and restart for a configuration update.   In
    WOLAChannel.stop() method, if called for a quiesce, the
    WOLAChannel posts an EVENT of the change.  This EVENT is an
    asynchronous piece of work that may be processed after the
    deactivation and re-activation of the WOLA Channel.   If the
    EVENT is processed after the WOLA Channel has been restarted
    then it will cause the WOLA Channel to stop.  The result is
    that communication over WOLA will be not be possible.
    

Local fix

  • 
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty for z/OS                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Cannot get a WOLA connection for a      *
    *                      client after configuration update       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There is a timing window during the WOLA Channel shutdown and
    restart for a configuration update.   In WOLAChannel.stop()
    method, if called for a quiesce, the WOLAChannel posts an EVENT
    for the state change.  This EVENT is an asynchronous piece of
    work that may be processed after the deactivation and re-
    activation of the WOLA Channel.   If the EVENT is processed
    after the WOLA Channel has been restarted then it will cause
    the
    WOLA Channel to stop.  The result is that communication over
    WOLA will be not be possible.
    

Problem conclusion

  • Code has been modified in the WOLAChannel.stop() method to not
    post an EVENT for ChannelFramework.EVENT_STOPCHAIN.  This will
    allow normal shutdown and restart processing of the WOLA
    channel.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 21.0.0.12.  Please refer to the Recommended Updates page
    for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • A restart of the Liberty server would correct the state of the
    WOLA Channel.   Also, as this problem is a timing problem,
    another configuration update to the WOLA configuration would
    drive the deactivation and re-activation of the WOLA channel;
    this may correct the state of the WOLA channel.
    

Comments

  • 
    

APAR Information

  • APAR number

    PH41840

  • Reported component name

    LIBERTY PROF -

  • Reported component ID

    5655W6514

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-11-03

  • Closed date

    2021-11-09

  • Last modified date

    2021-12-01

  • 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 PROF -

  • Fixed component ID

    5655W6514

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"CD0"}]

Document Information

Modified date:
02 December 2021