IBM Support

PI78260: Liberty JAXB-2.2 feature does not expose some XLXP2 packages

Fixes are available

17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the third party JPA provider (hibernate) with
    Liberty, the customer got the following exception:
    
    Caused by: javax.xml.stream.FactoryConfigurationError:
    Provider javax.xml.stream.XMLEventFactory could not be
    instantiated: java.util.ServiceConfigurationError:
    javax.xml.stream.XMLEventFactory: Provider
    com.ibm.xml.xlxp2.api.stax.XMLEventFactoryImpl not found
    at javax.xml.stream.XMLEventFactory.newFactory(Unknown
    Source)
    at javax.xml.stream.XMLEventFactory.newInstance(Unknown
    Source)
    at
    org.hibernate.boot.jaxb.internal.MappingBinder.<init>(Mappin
    gBinder.java:40)
    
    The issue is that
    com.ibm.xml.xlxp2.api.stax.XMLEventFactoryImpl is being
    picked up as the resource service for
    javax.xml.stream.XMLEventFactory, but the
    com.ibm.xml.xlxp2.api.stax; package is not being exposed to
    the application and its shared libraries, hence the
    "Provider not found" exception.
    

Local fix

  • None available
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty who use the jaxb-2.2         *
    *                  feature                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: javax.xml.stream.FactoryConfigurationEr *
    *                      ror occurs when using jaxb-2.2 feature  *
    *                      with hibernate                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Some xlxp2 packages were not exported by the jaxb-2.2 feature
    which caused the error:  Provider
    javax.xml.stream.XMLEventFactory could not be instantiated
    

Problem conclusion

  • The problem was fixed by exposing the following xlxp2 packages
    in jaxb-2.2 feature:  com.ibm.xml.xlxp2.api.jaxb,
    com.ibm.xml.xlxp2.api.stax, com.ibm.xml.xlxp2.api.wssec,
    com.ibm.xml.xlxp2.jaxb
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.0.0.2.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • There is no workaround available
    

Comments

APAR Information

  • APAR number

    PI78260

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-15

  • Closed date

    2017-05-09

  • Last modified date

    2017-05-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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021