IBM Support

PI87504: JAXRS server response does not contain a Servlet exception when an unmapped checkedException occurs

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Section 3.3.4 of the JAXRS 2.0 specification indicates the
    following:
    "4. Checked exceptions and throwables that have not been
    mapped and cannot be thrown directly MUST
    be wrapped in a container-specific exception that is then
    thrown and allowed to propagate to the underlying
    container. Servlet-based implementations MUST use
    ServletException as the wrapper.
    JAX-WS Provider-based implementations MUST use
    WebServiceException as the wrapper."
    Currently the Liberty JAXRS 2.0 server only returns an HTTP
    500 message in this situation.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty - JAX-RS                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: JAXRS server response does not contain  *
    *                      a Servlet exception when an unmapped    *
    *                      checkedException occurs                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Section 3.3.4 of the JAXRS 2.0 specification indicates the
    following:
    "4. Checked exceptions and throwables that have not been mapped
    and cannot be thrown directly MUST
    be wrapped in a container-specific exception that is then thrown
    and allowed to propagate to the underlying
    container. Servlet-based implementations MUST use
    ServletException as the wrapper.
    JAX-WS Provider-based implementations MUST use
    WebServiceException as the wrapper."
    Currently the Liberty JAXRS 2.0 server only returns an HTTP 500
    message in this situation.
    

Problem conclusion

  • The code was changed such that the client will now receive a
    ServletException nesting the original checked exception.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.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

    PI87504

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-18

  • Closed date

    2017-09-25

  • Last modified date

    2017-09-25

  • 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

  • RCD0 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":"CD0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 June 2020