IBM Support

PI69939: Dynamic Routing stops working when the collective controller becomes stopped or unavailable

Fixes are available

9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Dynamic Routing stops working when the collective controller
    becomes stopped or unavailable
    

Local fix

  • Create more collective controllers in a high availability
    configuration.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Plugin with Intelligent Management   *
    *                  running on Microsoft Windows operating      *
    *                  systems                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Dynamic Routing stops working when the  *
    *                      collective controller becomes stopped   *
    *                      or unavailable.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Intelligent Management enabled plugin learns of dynamic
    changes in routing information from XDAgent connectors (either
    Liberty Controllers or traditional WebSphere deployment managers
    or node agents).  It then uses this routing information to
    select the appropriate endpoint for incoming requests.  If
    communication is lost to the connector providing the dynamic
    routing information the plugin is still able to continue to
    route using the stale data until the plugin is restarted (at
    which point it is normal to not be able to route if we cannot
    obtain routing information from the connector).  However, on
    Windows operating systems there was an error that prevented
    routing from continuing when communication to the connector was
    lost.  This resulted not only in the loss of dynamic updates to
    routing information but also the complete loss of the ability to
    route even using the stale routing data.
    

Problem conclusion

  • The product has been updated so that the IBM WebSphere
    Application Server Plugin with Intelligent Management enabled
    and running on Microsoft Windows can continue to route requests
    using the last known routing information from the connector can
    continue even when communication with the connector is no longer
    possible.  Naturally this routing is only possible as long as
    the plugin remains active and routing will only be able to make
    use of the last known routing information prior to the connector
    becoming unavailable. Please note that the connector must be
    available to obtain some initial routing information for this
    limited routing capability to process in this failure state.  If
    a connector is not available at the startup of the plugin there
    will be no routing information available and no request will be
    able to be routed until communication between the plugin and the
    connector has been restored.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.11.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Ensure that there are multiple connectors so that routing
    information will always be available.  In a Liberty environment
    this involves creating a replica set to ensure that some
    controller is always available and able to provide routing
    information.  In a traditional WebSphere environment this
    involves ensuring that the Deployment Manager and one or more
    Node Agents are always available.
    

Comments

APAR Information

  • APAR number

    PI69939

  • 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-09-29

  • Closed date

    2016-11-22

  • Last modified date

    2016-11-22

  • 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:
23 November 2021