PH06673: WORKITEM.GETRESULT MAY RETURN NULL AND THIS CAUSE NPE IN CUSTOMER'S ASYNCBEAN APPLICATION.

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
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Even though the customer uses waitForAll API of CommonJ so that
  it wait for the completion of all works, there is a chance that
  WorkItem.getResult returns null even after waitForAll returns
  true. This behavior may cause the unexpected NPE in the
  customer's asyncbean application.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of CommonJ WorkManager in IBM     *
  *                  WebSphere Application Server                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Timing window after waitForAll where    *
  *                      getResult returns null                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  There is a small timing window after the WorkManager
  waitForAll method returns indicating all work is complete
  where querying a WorkItem's getResult method can return NULL,
  indicating that the work is not yet complete.
  

Problem conclusion

• Code fixed to avoid the timing window.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.11 and 8.5.5.16.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP