IBM Support

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

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

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

Temporary fix

Comments

APAR Information

  • APAR number

    PI91292

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-12-08

  • Closed date

    2018-01-09

  • Last modified date

    2018-01-09

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 900

Reference #: PI91292

Modified date: 09 January 2018


Translate this page: