IBM Support

PI08655: ODC violation exceptions (ODCF0002E) in SystemOut.log and FFDC e ntries (ProbeId:Problem applying ODC events) fill logs and disk.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When other components update On-Demand Configuration (ODC) data
    
    ODCTreeImpl   W   ODCF0002E: Exception: ODC violation from JSONX
    ODC violation 1: missing required property 'type' on node /cell/
    ODC violation 2: missing required parent 'cluster' on node /cell
    Transaction: JSONXService.setURL cellAgentUrl from cellName\node
    
    This can but rarely will result in nearly all other processes in
    
    FFDC Exception:com.ibm.wsspi.odc.ODCException SourceId:com.ibm.w
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Virtual          *
    *                  Enterprise.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: ODC violation exceptions (ODCF0002E) in *
    *                      SystemOut.log and FFDC entries          *
    *                      (ProbeId:Problem applying ODC events)   *
    *                      fill logs and disk.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When other components update On-Demand Configuration (ODC) data
    prior to ODC being fully initialized (i.e. the ODC tree is not
    yet well formed) "ODC violations" such as the one below can
    occur.
    ODCTreeImpl   W   ODCF0002E: Exception: ODC violation from
    JSONXService.setURL cellAgentUrl from
    cellName\nodeName\serverName
    ODC violation 1: missing required property 'type' on node
    /cell/cellName/node/nodeName/server/serverName
    ODC violation 2: missing required parent 'cluster' on node
    /cell/cellName/node/nodeName/server/serverName
    Transaction: JSONXService.setURL cellAgentUrl from
    cellName\nodeName\serverName:4
    This can but rarely will result in nearly all other processes in
    the cell rejecting ODC tree response messages coming from the
    process where the ODC violation (ODCF0002E) occurred, which can
    fill the file system with FFDC entries similar to the one
    below.
    FFDC Exception:com.ibm.wsspi.odc.ODCException
    SourceId:com.ibm.ws.odc.nd.ODCTreeImpl ProbeId:Problem applying
    ODC events from getTreeResponse from
    cellName\nodeName\serverName; BEGIN_TARGET_XML_BASE64:
    

Problem conclusion

  • ODC has been altered to protect itself from updates made by othe
    components before the tree is well formed.
    
    This fix will be included in the next available fix pack for IBM
    WebSphere Virtual Enterprise.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI08655

  • Reported component name

    WAS VIRTUAL ENT

  • Reported component ID

    5725C9203

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-12-23

  • Closed date

    2014-01-27

  • Last modified date

    2014-01-27

  • 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

    WAS VIRTUAL ENT

  • Fixed component ID

    5725C9203

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSUP64","label":"WebSphere Virtual Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022