IBM Support

PI83389: JAXBException error occurred when a JAXB class was not included in JAXBContext.

Fixes are available

9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
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
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
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
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When processing a response, a javax.xml.bind.JAXBException was
    thrown indicating that an application class was not known to
    the JAXBContext.  The error looked like the following example:
    
    javax.xml.bind.JAXBException:
    com.ibm.test.ReleaseDeficiencyResponse is not known to this
    context
    at
    com.ibm.jtc.jax.xml.bind.v2.runtime.JAXBContextImpl.getBeanInfo(
    JAXBContextImpl.java:621)
    at
    com.ibm.jtc.jax.xml.bind.v2.runtime.unmarshaller.UnmarshallerImp
    l.getBeanInfo(UnmarshallerImpl.java:623)
    at
    com.ibm.jtc.jax.xml.bind.v2.runtime.unmarshaller.UnmarshallerImp
    l.unmarshal(UnmarshallerImpl.java:402)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server for JAX-WS Web services.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: JAXBException error occurred when a     *
    *                      JAXB class was not included in          *
    *                      JAXBContext.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When processing a response, a javax.xml.bind.JAXBException was
    thrown indicating that an application class was not known to
    the JAXBContext.  This error occurred because incorrect
    classloader was used to load classes for JAXBContext, and some
    classes were not included in the JAXBContext.
    

Problem conclusion

  • JAX-WS runtime code has been updated to use the correct
    classloader to load classes for JAXBContext.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.13 and 9.0.0.6.  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

    PI83389

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-20

  • Closed date

    2017-10-12

  • Last modified date

    2017-10-12

  • 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

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 May 2022