PM60934: INVALID PLUGIN VERSION CAUSED FILENOTFOUNDEXCEPTION

6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• After redeploying ears containing extensions (plugin.xml),
  a server restart will cause multiple FileNotFound Exceptions
  in
  /opt/websphere-61/profiles/profile/temp/node/server
  /_extensionregistry/
  A second restart will fix the problem. The problem can
  reliably be reproduced by redeploying the ear and restarting.
  
  If the plugin.xml file is with a two digit version="x.y" value,
  there are issues starting the application the first time.
  IF the plugin.xml has a three digit value the applicaiton
  startup issue does not occur
  
  E   CWXRS0016E: Failed to read stored object: plg___2046367541
  
      java.io.FileNotFoundException:
  /opt/websphere-61/profiles/n1devc61/temp/sl001322n1/WebSphere_Po
  rtal
  /_extensionregistry/plg___2046367541.ser
   (No such file or directory)
  

Local fix

• change the plugin.xml with two digits to three digits
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  version 6.1.0.x                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Invalid version format in plugin.xml    *
  *                      caused FileNotFoundException            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The version number of a plugin.xml should be defined in three
  digits (like 1.0.0). If the version number format is less than
  three digits Extension Registry generates the wrong cache file
  ID and throws a FileNotFoundException.
  

Problem conclusion

• The fix will validate the version number format and logs a
  meaningful message in the trace if it is invalid, instead of a
  FileNotFoundException
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.45.  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

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP