PI95982: TIMER.GETINFO() NOT PROPERLY RETURNING NEW INSTANCE

9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
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

APAR status

• Closed as program error.

Error description

• Timer.getInfo() can unreliably return a cached instance in
  WebSphere Application Server version 8.5.5. The fix will
  change the the behavior to always return a new instance of the
  timer info.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server relying on data returned from        *
  *                  Timer.getInfo() inside an EJB persistent    *
  *                  timer timeout method.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Timer.getInfo() not properly            *
  *                      returning new instance inside           *
  *                      persistent timer timeout methods.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Timer.getInfo() can unreliably return a cached instance in
  WebSphere Application Server version 8.5.5. The fix will
  change the behavior to always return a new instance of the
  TimerInfo object.
  Before the fix, if a customer modifies the object returned by
  timer.getInfo(), they can unreliably receive the modified
  version the next time they call timer.getInfo() in subsequent
  timer timeout methods, when timerInfo should not be modifiable
  

Problem conclusion

• The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.15 and 9.0.0.10.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• A valid workaround is to not modify the
  object returned by Timer.getInfo()
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP