PI66884: APPLICATION START FAILS WITH UNDEFINEDVARIABLEEXCEPTION

9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
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
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• Application start fails when the MANIFEST.MF of the
  application contains a ${...} variable for the
  Implementation-Version attribute.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Application start fails if the          *
  *                      MANIFEST.MF of the application          *
  *                      contains a variable in the              *
  *                      Implementation-Version attribute.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The application server reads the application
  MANIFEST.MF file during deployment and stores the value of the
  "Implementation-Version" attribute in the application
  deployment file (deployment.xml).  The problem occurs when
  this attribute contains a variable name prefixed by a "$"
  character; for example: $version. During the start of the
  application, the application server reads the deployment.xml
  file.  When it encounters a variable (prefixed by a "$"), it
  interprets that as a WebSphere Application Server variable.
  Apart from an unlikely coincidence, that variable will not be
  found, which will halt processing of the application start.
  In the SystemOut.log, the following exception will be found.
  MBeanHelper   E   Could not invoke an operation on object:
  WebSphere:name=ApplicationManager,process=server1,platform=proxy
  ,node=wannabeeNode03,version=9.0.0.0,type=ApplicationManager,mbe
  anIdentifier=ApplicationManager,cell=wannabeeNode02Cell,spec=1.0
  because of an mbean exception:
  com.ibm.ws.exception.RuntimeError:
  com.ibm.wsspi.runtime.variable.UndefinedVariableException:
  Undefined variable version
  

Problem conclusion

• The application server code has been modified to include an
  extra "$" for any "$" read from the MANIFEST.MF file
  Implementation-Version attribute before writing the value to
  the deployment.xml.   For example, if the value of the
  Implementation-Version attribute is "$version", then
  "$$version" will be written to deployment.xml.  When reading
  $$version from the deployment.xml, the application server code
  removes the first $, but does not treat $version as a variable.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.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:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R900 PSY

     UP