IBM Support

PK82642: PROXY ODC COMPONENT FAILED TO GET COMPLETE ROUTING INFOMATION EVEN AFTER STARTUP DELAY ON Z/OS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The proxy server ODC component never gets complete routing
    information on z/OS.  This will manifest itself as a long
    delay on startup of the proxy server.  The proxy server will
    wait the entire duration of http.odcUpdateTimeout (default 90
    seconds) on startup.
    

Local fix

  • Lower the http.odcUpdateTimeout to a small value to work around
    this issue.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere Application Server    *
    *                 V7.0                                         *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Proxy routing data is not fully         *
    *                      received at startup on z/OS.            *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the proxy server starts up, it waits for the routing
    information about the back-end cell to be received. This wait
    requires async reads to complete; on z/OS, however, the
    threads that handle async reads do not start until after the
    proxy initiates this wait.
    

Problem conclusion

  • This fix solves the issue by moving the code that starts the
    proxy's chains and waits for routing data to be received to
    start after the z/OS native threads that handle async reads.
    With this fix, the proxy will have its full routing tree by
    the time the proxy server starts.
    
    APAR PK82642 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.3 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK82642

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-16

  • Closed date

    2009-03-19

  • Last modified date

    2009-05-03

  • APAR is sysrouted FROM one or more of the following:

    PK71680

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • BBGUBINF BBOUBINF
    

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK45160

       UP09/04/06 P F904

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022