IBM Support

PI83444: JAXRS SERVER RESPONSE DOES NOT CONTAIN A SERVLET EXCEPTION WHEN AN UNMAPPED CHECKED EXCEPTION OCCURS

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

  • 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

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server who use the JAXRS 2.0 feature        *
    *                  function.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: JAXRS 2.0 server returns only an        *
    *                      HTTP 500 message when the               *
    *                      specification indicates that a          *
    *                      ServletException is returned.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    JAXRS 2.0 server returns only an HTTP 500 message when a
    checked exception is thrown.
    Section 3.3.4 of the JAXRS 2.0 specification indicates that a
    ServletException should be thrown.
    

Problem conclusion

  • The Liberty code was modified to return a ServletException as
    indicated by the JAXRS 2.0 specification.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.0.5.  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

    PI83444

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-21

  • Closed date

    2017-08-10

  • Last modified date

    2017-08-17

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R900 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 900

Reference #: PI83444

Modified date: 17 August 2017


Translate this page: