IBM Support

PI66702: MULTI-ADDRESS CORBANAME URLS DO NOT FAIL OVER TO THE SECOND ADDRESS WHEN THE FIRST ADDRESS SERVER IS DOWN

Fixes are available

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

  • When resolving up a multi-address corbaname: or corbaloc:
    URL, the Yoko ORB in Liberty attempts a lookup of the remote
    name service at the first address. If this fails with a
    TRANSIENT exception (e.g. due to the server being stopped)
    the processing escapes the retry logic and no connection is
    attempted to the second and subsequent addresses.
    
    The error seen will be of the form:
    
    org.omg.CORBA.BAD_PARAM: other: corbaname evaluation
    error:attempt to establish connection failed Error
    connecting to host
    
    amongst the stack trace will be:
    
    Caused by: org.omg.CORBA.TRANSIENT: attempt to establish
    connection failedError connecting to host
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users using Liberty EJB support to access   *
    *                  clustered EJBs in WAS classic               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Liberty cannot invoke clustered EJBs in *
    *                      WAS classic, failing with CORBA         *
    *                      exceptions TRANSIENT and BAD_PARAM.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Liberty cannot invoke clustered EJBs in WAS classic, failing
    with CORBA exceptions TRANSIENT and BAD_PARAM.
    
    This happens because the code to handle multi-endpoint IORs in
    Liberty does not involve the Yoko ORB and the Yoko ORB sees all
    possible connections as being to the first endpoint. Yoko caches
    these incorrectly, and other, subsequent messages are
    misdirected to an invalid endpoint.
    

Problem conclusion

  • The Yoko ORB is modified to accept multi-endpoint IORs and cache
    the connections in an endpoint-specific way. The logic to select
    an endpoint is removed from the Liberty code. Yoko now queries
    the Liberty plugin for a description of all the endpoints and
    queries each in turn.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.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

  • Use only standalone WAS classic server instances or change the
    client's lookup string to use the server-specific naming context
    to retrieve a reference to a single IOR. Do NOT use multi-
    address corbanames (no failover).
    

Comments

APAR Information

  • APAR number

    PI66702

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-01

  • Closed date

    2017-05-23

  • Last modified date

    2017-05-23

  • 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

  • R850 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":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 October 2021