PM60456: ASYN0080W LOGGED DURING JVM STARTUP

8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• ASYN0080W logged during JVM startup.
  This warnings are getting printed incorrectly by the WebSphere
  asynchbeans component and it should not be happening.
  It is not related to the user application and we do not expect
  any functionality loss due to this warning message.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: ASYN0080W warning messages noticed      *
  *                      during server startup                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The following ASYN0080W warning message can be noticed in the
  SystemOut.log during server startup.
  [10/14/11 4:05:19:671 EDT] 00000000 J2EEServiceMa W
  ASYN0080W: Registration of the JTA service might not be
  honored because the service was registered after asynchronous
  beans was used.
  [10/14/11 4:05:19:687 EDT] 00000000 J2EEServiceMa W
  ASYN0080W: Registration of the JavaCompContextMgr service
  might not be honored because the service was registered after
  asynchronous beans was used.
  

Problem conclusion

• These warning messages were incorrectly logged during server
  startup and the code has been updated to avoid these warning
  messages.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.5.  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 EXPRESS

• Fixed component ID

  5724I6300

Applicable component levels

• R800 PSY

     UP