PM41752: SDO CHANGE SUMMARY HANDLING MAY CAUSE XPROCESSEXCEPTION

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• SDO change summary handling may cause XProcessException
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM Business Process Manager and            *
  *                  WebSphere Enterprise Service Bus            *
  *                  customers using Lazy Parsing Mode           *
  ****************************************************************
  * PROBLEM DESCRIPTION: SDO change summary handling may cause   *
  *                      XProcessException                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Under some circimstances, initialization of an SDO change
  summary could cause an XProcessException with the following
  message:
  
  com.ibm.xml.xapi.XProcessException: IXJXE0920E: [ERR API0136]
  Execution terminated because of the following error:
  'IXJXE1020E: [ERR 0777][ERR XPDY0050] A path expression begins
  with '/' or '//' but the context node is not in a tree that is
  rooted at a document node.; SystemID: unknown; Line#: 1;
  Column# 1'
  
  This was possible because SDO datagraphs are not always rooted
  at a document node.
  

Problem conclusion

• The change summary initialization code has been improved to
  make sure that an SDO datagraph is rooted at a document node
  before attempting to evaluate an absolute XPath expression.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.1.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

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

  PM38507

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

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY