IBM Support

PI55049: Non-persistent EJB Timer created while application is stopping m ay not be removed

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an application is stopped, all non-persistent EJB
    timers should be removed. However, if a running application
    is in the process of creating non-persistent timers at
    exactly the same time the application is stopping, then
    those non-persistent timers may not be removed.
    
    The remaining non-persistent timers will never run, however
    they will remain in memory until the server process is
    stopped. If the same application is started gain, the
    existing timers will still not run, but they may be returned
    on a call to EJBContext.getTimers().
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile - Enterprise Java    *
    *                  Beans (EJB)                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Non-persistent EJB Timer created while  *
    *                      application is stopping may not be      *
    *                      removed                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an application is stopped, all non-persistent EJB timers
    should be removed. However, if a running application is in the
    process of creating non-persistent timers at exactly the same
    time the application is stopping, then those non-persistent
    timers may not be removed.
    
    The remaining non-persistent timers will never run, however they
    will remain in memory until the server process is stopped. If
    the same application is started again, the existing timers will
    still not run, but they may be returned on a call to
    EJBContext.getTimers().
    

Problem conclusion

  • The EJB container runtime has been updated to remove all non-
    persistent timers for an application when the application is
    stopped, including those non-persistent timers that may be
    created concurrently with application stop processing.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.10.  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

    PI55049

  • 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

    2016-01-07

  • Closed date

    2016-01-13

  • Last modified date

    2016-01-13

  • 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 \u0026 Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 October 2021