PM53690: ORG.XML.SAX.SAXPARSEEXCEPTION IS RECEIVED WHEN DUMPING A BUSINESS OBJECT

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

• When trying to dump a Business Object (BO) with empty data in
  the response message, the following exception is thrown in
  SystemErr.log:
  
  [11/25/11 21:51:13:781 JST] 0000003d SystemErr     R
  
  org.xml.sax.SAXParseException: The element type
  "ns0:aaaaaResponse" must be terminated by
  the matching end-tag "</ns0:aaaaaResponse>".
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: An issue in the serialization           *
  *                      optimizer caused an incorrect output    *
  *                      for a parsed object tree that had       *
  *                      deleted nodes.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During a specific scenario where the input XML contained
  various nested elements and some of these nodes were moved
  into another tree, the serialization that followed was
  incorrect because parts of the deleted region were still
  present.
  

Problem conclusion

• The optimizations for the serializer now properly handle all
  mutations at all levels of the input so that the serialization
  output does not include deleted nodes.
  
  The fix for this APAR is currently targeted for inclusion
  in fix pack 8.0.0.5.  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:

  PM52927

• 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

     UP