PI91292: SAXPARSEEXCEPTION FOR A TAG LIBRARY DOES NOT DISPLAY THE FILE NAME

9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• If a problem occurs while parsing a tag library
  (.tld
  file) in a WAR, a SAXParseException is thrown, but the name of
  the WAR
  and the name of the .tld file are not displayed making debugging
  difficult.  An error message says "error parsing faces-config",
  but the
  message is incorrect.
  
  
  [17/10/19 10:56:46:253 JST] 00000082 annotations   E
  BasicTagHandler
  fatalError error parsing faces-config
                                   org.xml.sax.SAXParseException:
  
   at
  org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseExcepti
  on(Unkno
  wn Source)
   at
  org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
  Source)
   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
  Source)
   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
  Source)
   at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown
  Source)
   at
  org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.d
  ispatch(
  Unknown Source)
   at
  org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume
  nt(Unkno
  wn Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
  Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
  Source)
   at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
   at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
  Source)
   at
  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
  Source)
   at
  com.ibm.ws.amm.scan.context.WARScannerContext.collectTagLibClass
  esSetPro
  cessClassNames(WARScannerContext.java:445)
   at
  com.ibm.ws.jsp.cdi.JSPInjectionClassListCollaborator.getInjectio
  nClasses
  (JSPInjectionClassListCollaborator.java:67)
   at
  com.ibm.ws.cdi.classic.CDIArchiveImpl.getInjectionClassList(CDIA
  rchiveIm
  pl.java:77)
   at
  com.ibm.ws.cdi.impl.weld.BeanDeploymentArchiveImpl.initializeJEE
  Componen
  tClasses(BeanDeploymentArchiveImpl.java:400)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server containing an application with an    *
  *                  invalid tag library                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: A SAXParseException is thrown when      *
  *                      parsing a tag library, but the error    *
  *                      message is incomplete.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a problem occurs while parsing a tag library (.tld file) in
  a WAR, a SAXParseException is thrown, but the name of the WAR
  and the name of the .tld file are not displayed making
  debugging
  difficult.  An error message says "error parsing faces-config",
  but the message is incorrect.
  [17/10/19 10:56:46:253 JST] 00000082 annotations   E
  BasicTagHandler
  fatalError error parsing faces-config
  org.xml.sax.SAXParseException:
  at
  org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseExcepti
  on(Unkno
  wn Source)
  at
  org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
  Source)
  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
  Source)
  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
  Source)
  at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown
  Source)
  at
  org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.d
  ispatch(
  Unknown Source)
  at
  org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume
  nt(Unkno
  wn Source)
  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
  Source)
  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
  Source)
  at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
  at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
  Source)
  at
  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
  Source)
  at
  com.ibm.ws.amm.scan.context.WARScannerContext.collectTagLibClass
  esSetPro
  cessClassNames(WARScannerContext.java:445)
  at
  com.ibm.ws.jsp.cdi.JSPInjectionClassListCollaborator.getInjectio
  nClasses
  (JSPInjectionClassListCollaborator.java:67)
  at
  com.ibm.ws.cdi.classic.CDIArchiveImpl.getInjectionClassList(CDIA
  rchiveIm
  pl.java:77)
  at
  com.ibm.ws.cdi.impl.weld.BeanDeploymentArchiveImpl.initializeJEE
  Componen
  tClasses(BeanDeploymentArchiveImpl.java:400)
  

Problem conclusion

• The message has been updated to display the name of the tag
  library file and the WAR file.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.7.  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:

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

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R900 PSY

     UP