PI09105: ASYN0090I LOGGED AT 1ST INVOCATION OF ASYNCBEAN

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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 invoking an AsyncBean, the ASYN0090I indicator is always
  logged with a very old timestamp (Thu Jan 01 09:00:00 JST 1970)
  
  -----
  Work manager xx/XXWorkManager is running work item
  {1} later than expected. The work item was submitted
  at 0(Thu Jan 01 09:00:00 JST 1970) and is starting to
  run at {3}.
  -----
  
  This should not be printed.
  

Local fix

• Call this method with "isDaemon = false"
    com.ibm.websphere.asynchbeans.WorkManager
    .startWork(Work e, long startTimeOut_ms,
     WorkListener wl,  boolean isDaemon)
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the asyncbean work is submitted    *
  *                      to run as daemon thread, ASYN0090I      *
  *                      is printed with a very old timestamp    *
  *                      (Thu Jan 01 09:00:00 JST 1970)          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the work is submitted to run as daemon thread it is
  displaying an ASYN0090I message with a very old timestamp
  (Thu Jan 01 09:00:00 JST 1970) as the submitted timestamp.
  When the work is submitted to the thread pool, the submitted
  work time is updated. When the work is submitted to run as
  a daemon thread the submitted work time is not updated and it
  has the default time.
  

Problem conclusion

• The problem is fixed by adding a check and printing ASYN0090I
  only when the submitted time is not zero.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.2.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP