PH01284: CLEAN SERVER OSGI CACHE ON RESTART AFTER HARD SHUTDOWN

9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
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

• Server fails to start after hard shutdown
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: The application server fails to start   *
  *                      after a hard shutdown.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an application server shuts down hard -- that is, when a
  server process terminates before the server executes the
  normal shutdown sequence -- the OSGi bundle cache for that
  server may corrupt.  A corrupted or stale bundle cache can
  cause an application server to fail to start or to exhibit
  unexpected behaviors that are difficult to determine.
  Typically you would resolve problems caused by a corrupt OSGi
  bundle cache by invoking the osgiCfgInit utility on the
  problematic server before starting the server. The utility
  deletes the server's cached bundle data and resets the data
  according to the server's bundle dependencies.
  You can also resolve these problems by setting generic JVM
  argument "-Dosgi.clean=true" in the problematic server's
  configuration. The setting enables WAS to reset the OSGI
  bundle cache while starting the server. This solution is less
  practical as it increases the elapsed time to start a server,
  but very practical after a server's OSGi bundle cache
  has become corrupted.
  APAR PH01284 reduces the chance that an application server
  will fail due to a corrupt OSGi bundle cache by setting
  JVM option "-Dosgi.clean=true" on server startup whenever it
  detects the server was shutdown hard during its previous
  execution.
  

Problem conclusion

• The startup processing was updated to clean the OSGI bundle
  cache if the last termination was not a graceful shutdown.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.15 and 9.0.0.10.  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