IBM Support

PH01610: APPLICATION FAILS TO START DUE TO JAXBEXCEPTION AFTER UPGRADING TO 18.0.0.2

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During 18.0.0.2 development a change was made to wimcore-1.0
    (a
    private feature included by federatedRegistry and
    ldapRegistry)
    to include Liberty's internal copy of JAX-B in preparation
    for
    Java 9+ support.
    

Local fix

  • Enable the public jaxb-2.2 feature and rely on the JDK copy
    of JAXB
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty - Runtime and Classloading   *
    ****************************************************************
    * PROBLEM DESCRIPTION: APPLICATION FAILS TO START DUE TO       *
    *                      JAXBEXCEPTION AFTER UPGRADING TO        *
    *                      18.0.0.2                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After upgrading from 18.0.0.1 to 18.0.0.2, some users
    encountered a JAXB error when we try to explicitly load
    JAXBContext. The issue typically occured on application startup
    time, with a stack trace as follows:
    
    java.lang.Error: javax.xml.bind.JAXBException: Unable to create
    context
     - with linked exception:
    [java.lang.reflect.InvocationTargetException]
    	at
    com.example.model.util.FHIRUtil.createContext(FHIRUtil.java:225)
    at com.example.model.util.FHIRUtil.<clinit>(FHIRUtil.java:147)
    	at
    com.example.server.listener.FHIRServletContextListener.contextIn
    itialized(FHIRServletContextListener.java:74)
    	at
    com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreate
    d(WebApp.java:2376)
    	at
    com.ibm.ws.webcontainer31.osgi.webapp.WebApp31.notifyServletCont
    extCreated(WebApp31.java:514)
    	at
    com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:100
    4)
    	at
    com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:656
    6)
    	at
    com.ibm.ws.webcontainer.osgi.DynamicVirtualHost.startWebApp(Dyna
    micVirtualHost.java:467)
    	at
    com.ibm.ws.webcontainer.osgi.DynamicVirtualHost.startWebApplicat
    ion(DynamicVirtualHost.java:462)
    	at
    com.ibm.ws.webcontainer.osgi.WebContainer.startWebApplication(We
    bContainer.java:1132)
    	at
    com.ibm.ws.webcontainer.osgi.WebContainer.startModule(WebContain
    er.java:937)
    	at
    com.ibm.ws.app.manager.module.internal.ModuleHandlerBase.deployM
    odule(ModuleHandlerBase.java:99)
    	at
    com.ibm.ws.app.manager.module.internal.DeployedModuleInfoImpl.in
    stallModule(DeployedModuleInfoImpl.java:49)
    	at
    com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase.deplo
    yModules(DeployedAppInfoBase.java:429)
    	at
    com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase.deplo
    yApp(DeployedAppInfoBase.java:415)
    	at
    com.ibm.ws.app.manager.war.internal.WARApplicationHandlerImpl.in
    stall(WARApplicationHandlerImpl.java:65)
    	at
    com.ibm.ws.app.manager.internal.statemachine.StartAction.execute
    (StartAction.java:140)
    	at
    com.ibm.ws.app.manager.internal.statemachine.ApplicationStateMac
    hineImpl.enterState(ApplicationStateMachineImpl.java:1258)
    	at
    com.ibm.ws.app.manager.internal.statemachine.ApplicationStateMac
    hineImpl.run(ApplicationStateMachineImpl.java:873)
    	at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1160)
    	at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:635)
    	at java.lang.Thread.run(Thread.java:811)
    Caused by: javax.xml.bind.JAXBException: Unable to create
    context
     - with linked exception:
    [java.lang.reflect.InvocationTargetException]
    	at javax.xml.bind.ContextFinder.find(ContextFinder.java:70)
    	at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:77)
    	at
    com.example.model.util.FHIRUtil.createContext(FHIRUtil.java:223)
    ... 21 more
    Caused by: java.lang.reflect.InvocationTargetException
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:90)
    	at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:55)
    	at java.lang.reflect.Method.invoke(Method.java:508)
    	at javax.xml.bind.ContextFinder.find(ContextFinder.java:66)
    	... 23 more
    Caused by: javax.xml.bind.JAXBException:
    Descriptor Exceptions:
    ---------------------------------------------------------
    
    Runtime Exceptions:
    ---------------------------------------------------------
    
    Exception [EclipseLink-50033] (Eclipse Persistence Services -
    2.6.4.v20160829-44060b6):
    org.eclipse.persistence.exceptions.JAXBException
    Exception Description: The DomHandlerConverter for DomHandler
    [javax.xml.bind.annotation.W3CDomHandler] set on property [div]
    could not be initialized.
    Internal Exception: java.lang.NoSuchMethodException:
    javax.xml.bind.annotation.W3CDomHandler.createUnmarshaller(javax
    .xml.bind.ValidationEventHandler)
    
     - with linked exception:
    [Exception [EclipseLink-0] (Eclipse Persistence Services -
    2.6.4.v20160829-44060b6):
    org.eclipse.persistence.exceptions.IntegrityException
    Descriptor Exceptions:
    ---------------------------------------------------------
    
    Runtime Exceptions:
    ---------------------------------------------------------
    
    Exception [EclipseLink-50033] (Eclipse Persistence Services -
    2.6.4.v20160829-44060b6):
    org.eclipse.persistence.exceptions.JAXBException
    Exception Description: The DomHandlerConverter for DomHandler
    [javax.xml.bind.annotation.W3CDomHandler] set on property [div]
    could not be initialized.
    Internal Exception: java.lang.NoSuchMethodException:
    javax.xml.bind.annotation.W3CDomHandler.createUnmarshaller(javax
    .xml.bind.ValidationEventHandler)
    ]
    	at
    org.eclipse.persistence.jaxb.JAXBContext$ContextPathInput.create
    ContextState(JAXBContext.java:961)
    	at
    org.eclipse.persistence.jaxb.JAXBContext$ContextPathInput.create
    ContextState(JAXBContext.java:893)
    	at
    org.eclipse.persistence.jaxb.JAXBContext.<init>(JAXBContext.java
    :193)
    	at
    org.eclipse.persistence.jaxb.JAXBContextFactory.createContext(JA
    XBContextFactory.java:129)
    	... 28 more
    Caused by: Exception [EclipseLink-0] (Eclipse Persistence
    Services - 2.6.4.v20160829-44060b6):
    org.eclipse.persistence.exceptions.IntegrityException
    Descriptor Exceptions:
    ---------------------------------------------------------
    
    Runtime Exceptions:
    ---------------------------------------------------------
    
    Exception [EclipseLink-50033] (Eclipse Persistence Services -
    2.6.4.v20160829-44060b6):
    org.eclipse.persistence.exceptions.JAXBException
    Exception Description: The DomHandlerConverter for DomHandler
    [javax.xml.bind.annotation.W3CDomHandler] set on property [div]
    could not be initialized.
    Internal Exception: java.lang.NoSuchMethodException:
    javax.xml.bind.annotation.W3CDomHandler.createUnmarshaller(javax
    .xml.bind.ValidationEventHandler)
    
    	at
    org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.in
    itializeDescriptors(DatabaseSessionImpl.java:715)
    	at
    org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.in
    itializeDescriptors(DatabaseSessionImpl.java:651)
    	at
    org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.in
    itializeDescriptors(DatabaseSessionImpl.java:582)
    	at
    org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.po
    stConnectDatasource(DatabaseSessionImpl.java:818)
    	at
    org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.lo
    gin(DatabaseSessionImpl.java:775)
    	at
    org.eclipse.persistence.oxm.XMLContext$XMLContextState.setupSess
    ion(XMLContext.java:749)
    	at
    org.eclipse.persistence.oxm.XMLContext$XMLContextState.setupSess
    ion(XMLContext.java:1)
    	at
    org.eclipse.persistence.internal.oxm.Context$ContextState.<init>
    (Context.java:80)
    	at
    org.eclipse.persistence.oxm.XMLContext$XMLContextState.<init>(XM
    LContext.java:712)
    	at
    org.eclipse.persistence.oxm.XMLContext.<init>(XMLContext.java:19
    4)
    	at
    org.eclipse.persistence.jaxb.JAXBContext$ContextPathInput.create
    ContextState(JAXBContext.java:986)
    	at
    org.eclipse.persistence.jaxb.JAXBContext$ContextPathInput.create
    ContextState(JAXBContext.java:959)
    	... 31 more
    

Problem conclusion

  • In preparation for Java 11 support, where JAX-B is being removed
    from the JDK, internal refactoring was ocurring on Liberty
    components. As a result of this refactoring, a split package
    classloading conflict started to occur for applications which
    packaged their own implementation of JAX-B.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 18.0.0.3.  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 number

    PH01610

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-13

  • Closed date

    2019-08-10

  • Last modified date

    2019-08-10

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 October 2021