PM41734: NULL POINTER EXCEPTION WHEN LOADING XML DOCUMENTS

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

• NullPointerException is thrown from the NamedDeclaration class
  when an XML document is loaded:
  
  com.ibm.xml.xlxp.internal.s1.grammar.NamedDeclaration.createMap
  (NamedDeclaration.java:123)
  com.ibm.xml.xlxp.internal.s1.grammar.Grammar.setGlobalTypes
  (Grammar.java:242)
  com.ibm.xml.xlxp.internal.s1.converter.Converter.fillGrammar
  (Converter.java:608)
  com.ibm.xml.xlxp.internal.s1.converter.Converter.convert
  (Converter.java:244)
  com.ibm.xml.xlxp.internal.s1.converter.Merger.convert
  (Merger.java:144)
  com.ibm.xml.xlxp.internal.s1.converter.MergerContext.
  convertGrammar(MergerContext.java:153)
  com.ibm.xml.xci.adapters.xlxp.util.XLXPResourceManager.
  getGrammars(XLXPResourceManager.java:93)
  com.ibm.xml.xci.adapters.xlxp.util.XLXPResourceManager.
  setupScanner(XLXPResourceManager.java:322)
  com.ibm.xml.xci.adapters.xlxp.XLXPCursorFactory.
  document(XLXPCursorFactory.java:93)
  com.ibm.xml.xci.adapters.xlxp.XLXPCursorFactory.
  document(XLXPCursorFactory.java:250)
  com.ibm.xml.xci.SessionContext.document(SessionContext.java:312)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the XML API for IBM WebSphere      *
  *                  Application Server V8.0                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Null pointer exception when loading     *
  *                      XML documents using the XML API.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an XML document is loaded using the XML code, or through
  another stack product that uses the XML code, sometimes the
  following exception may be thrown:
  
  com.ibm.xml.xlxp.internal.s1.grammar.NamedDeclaration.createMap(
  NamedDeclaration.java:123)
  com.ibm.xml.xlxp.internal.s1.grammar.Grammar.setGlobalTypes(Gram
  mar.java:242)
  com.ibm.xml.xlxp.internal.s1.converter.Converter.fillGrammar(Con
  verter.java:608)
  com.ibm.xml.xlxp.internal.s1.converter.Converter.convert(Convert
  er.java:244)
  com.ibm.xml.xlxp.internal.s1.converter.Merger.convert(Merger.jav
  a:144)
  com.ibm.xml.xlxp.internal.s1.converter.MergerContext.convertGram
  mar(MergerContext.java:153)
  com.ibm.xml.xci.adapters.xlxp.util.XLXPResourceManager.getGramma
  rs(XLXPResourceManager.java:93)
  com.ibm.xml.xci.adapters.xlxp.util.XLXPResourceManager.setupScan
  ner(XLXPResourceManager.java:322)
  com.ibm.xml.xci.adapters.xlxp.XLXPCursorFactory.document(XLXPCur
  sorFactory.java:93)
  com.ibm.xml.xci.adapters.xlxp.XLXPCursorFactory.document(XLXPCur
  sorFactory.java:250)com.ibm.xml.xci.SessionContext.document(Sess
  ionContext.java:312)
  ...
  

Problem conclusion

• The component that loads and assembles XML Schemas sometimes
  needs to create copies of the container objects to reuse
  schema components. When the copy occurs, other container
  objects that reference the original container object need to
  be updated to reference the new copy, to maintain consistency
  within the schema. There are cases where a copy is made but
  the references still point to the old object. When a schema
  containing these objects is used, it gets confused by the
  duplicate objects.
  
  The fix is to ensure the schema is always consistent by
  updating all relevant references when a container object is
  copied.
  
  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:

  PM36721

• 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