IBM Support

PK98681: ODC UPDATE TIMEOUT BLOCKS OTHER CHANNEL TO INITIALIZE IN THE MAIN THREAD, ROUTING INFORMATION COULD NOT BE POPULATED INTO ODC

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ODC update timeout blocks other channel to initialize in the
    main threas and routing information could be populated into ODC.
    On the WebSphere Proxy Server you receive a
    ODC_InCompleteInfoReceived.
    In a A good case shows in the logs:
    .
    Trace: 2009/04/28 12:45:27.116 01 t=BE3E88 c=UNK key=S2
    (13007002)
      ThreadId: 0000000a
      FunctionName: com.ibm.ws.odc.ODCTreeImpl
      SourceId: com.ibm.ws.odc.ODCTreeImpl
      Category: INFO
      ExtendedMessage: BBOO0222I: ODC_CompleteInfoReceived
    .
    In a failing case we still see in the logs:
    .
    Trace: 2009/04/28 13:04:57.086 01 t=BE3E88 c=UNK key=S2
    (13007002)
      ThreadId: 0000000a
      FunctionName: com.ibm.ws.odc.ODCTreeImpl
      SourceId: com.ibm.ws.odc.ODCTreeImpl
      Category: INFO
      ExtendedMessage: BBOO0222I: ODC_InCompleteInfoReceived
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere Application Server    *
    *                 V7.0                                         *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: ODC could not get complete routing      *
    *                      information when the proxy server is    *
    *                      started.                                *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There is a circular dependency among multiple ODR components
    on z/OS, which causes ODC component not being able to receive
    complete routing information.
    

Problem conclusion

  • In the fix, proxy channel created by other components will not
    wait for odc update to finish.
    
    APAR PK98681 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.7 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

    PK98681

  • 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-10-15

  • Closed date

    2009-10-21

  • Last modified date

    2009-12-02

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

    PK89935

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

       UP09/11/10 P F911

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