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

8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

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