PK26456: ASYNCHRONOUS BEANS DOES NOT ACTUALLY REGISTER ITSELF WITH THE CONTAINER.

6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for HP-UX
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for AIX
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Windows
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Linux
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for i5/OS
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Solaris

APAR status

• Closed as program error.

Error description

• Fact: Work objects can be defined as long-lived (daemon) by
  returning a value of true from the isDaemon() method. Daemon
  Works can outlive the Servlet request or EJB method that
  scheduled it, but will automatically be released when the
  application is stopped. These "Works" do not use a thread from a
  pool.
  
  Actual problem: It appears that 6.0.2 & forward that
  asynchronous beans does not actually register itself with the
  container and so never receives notification of the application
  being stopped in order to release daemon threads.
  

Local fix

• no work around provided
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: WebSphere Application Server version 6 users *
  *                 of asynchronous beans daemon work units.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: When stopping an EJB application,       *
  *                      asynchronous beans daemon work units    *
  *                      continue running and are not released.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When stopping an EJB application, asynchronous beans daemon
  work units continue running and are not released.
  

Problem conclusion

• Asynchronous Beans code has been fixed to detect when EJB
  applications are stopped, and, in response, release all
  daemon units of work for the application.
  
  The fix for this APAR is currently targeted for inclusion
  in fixpack 6.0.2.13 and 6.1.0.1.
  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:

Modules/Macros

• ASYNCBN
  

Fix information

• Fixed component name

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP