IBM Support

PI82239: NULLPOINTEREXCEPTION AFTER STOPPING ONE OF MULTIPLE JAXRS APPLICATIONS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If multiple JAXRS applications are installed in a WebSphere
    Application Server server, stopping one of the applications may
    cause the remaining JAXRS application to become unusable with a
    NullPointerException
    generated in the logs
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server with multiple JAXRS applications     *
    *                  within a single server.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Stopping one of multiple JAXRS          *
    *                      applications can cause others to        *
    *                      become unusable.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This problem only occurs when multiple JAX-RS
    applications are started within the same WebSphere server.
    The issue is triggered when one of the applications, other
    than the first one started, is stopped.  This will
    cause the first application, that is
    still running, to become disabled and a NullPointerException
    will appear in the logs.
    Upon analysis we determined that certain resources that were
    associated with the first application started were mistakenly
    removed when other applications were stopped.
    The resolution to the problem was to change the code that
    executed at application stop to remove only those resources
    associated with the application being stopped.
    

Problem conclusion

Temporary fix

  • This issue can be worked-around by stopping and restarting the
    WebSphere Application Server process.
    

Comments

APAR Information

  • APAR number

    PI82239

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-26

  • Closed date

    2017-06-09

  • Last modified date

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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVS22","label":"General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
09 June 2017