PK29555: HUNG JVM IGNORES SHUTDOWN HOOKS DURING HA MANAGER RECOVERY PROCESSING

6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Solaris
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for HP-UX
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Linux
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for Linux
6.1.0.3: WebSphere Application Server V6.1.0 Fix Pack 3 for Linux
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Windows
6.1.0.3: WebSphere Application Server V6.1.0 Fix Pack 3 for Windows
6.1.0.7 WebSphere Application Server V6.1 Fix Pack 7 for AIX
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for AIX
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for i5/OS
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for i5/OS
6.1.0.3: WebSphere Application Server V6.1.0 Fix Pack 3 for HP-UX
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for HP-UX
6.1.0.3: WebSphere Application Server V6.1.0 Fix Pack 3 for i5/OS
6.1.0.3: WebSphere Application Server V6.1.0 Fix Pack 3 for AIX
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for Windows
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
6.1.0.3: WebSphere Application Server V6.1.0 Fix Pack 3 for Solaris
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for Solaris
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris

APAR status

• Closed as program error.

Error description

• After JVM is shutdown by WebSphere as part of HA Manager, a
  hung thread prevents HA Manager from restarting an affected JVM
  for some period of time.
  
  Errors seen in the systemout.log shows for ten minutes, one each
  minute, a message
  
  "CWRLS0030W: Waiting for HAManager to activate recovery
  processing for
  local WebSphere server
  
  Finally after 10 minutes it appears to resume:
  
  [5/2/06 9:51:22:540 PDT] 00000087 RecoveryDirec I   CWRLS0010I:
  Performing recovery processing for local WebSphere server
  (servnameclone\clone\servername).
  [5/2/06 9:51:22:548 PDT] 00000087 RecoveryDirec I   CWRLS0012I:
  All
  persistent services have been directed to perform recovery
  processing
  for this WebSphere server (servnameclone\clone\server).
   0000001f RLSHAGroupCal W   CWRLS0030W:
  Waiting for HAManager to activate recovery processing for local
  WebSphere server
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: WebSphere Application Server version 6 users *
  *                 who leave hamanager enabled (the default     *
  *                 is enabled).                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: The JVM will not terminate, it hangs    *
  *                      when attempting to exit.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Situations can occur where the jvm must perform an emergency
  stop. On certain platforms, when an emergency stop is
  performed, there were long delays observed before the jvm
  actually exited. Historically the hamanager component has used
  the System.exit() mechanism for forcing jvm's to terminate in
  the event an emergency stop situation is detected; however,
  consistent behavior is not observed across all platforms.
  Using the halt() mechanism from the jdk runtime provides the
  desired cross-platform consistent behavior, and the jvm
  terminates as expected, without delay.
  

Problem conclusion

• When the HAManager is requested to terminate the jvm, it
  will now call Runtime.halt() instead of System.exit(). This
  eliminates the hang condition experienced.
  
  The fix for this APAR is currently targeted for inclusion
  in fixpacks 6.0.2.17 and 6.1.0.3.
  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

• HAMGR
  

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