PI34143: MODULE UPDATES REWRITE THE MODULE MANIFEST, META-INF/MANIFEST.MF

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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

• ABSTRACT:
  An application update which replaces a single module always
  rewrites the module manifest, META-INF/MANIFEST.MF.  The
  rewrite preserves manifest values, but does not preserve the
  exact format of the manifest.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: A single module update always rewrites  *
  *                      the module manifest, potentially        *
  *                      changing manifest characters.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When updating an application using the option to add or replace
  a single module, processing may update the module manifest.
  The module manifest is the file "META-INF/MANIFEST.MF".  A
  manifest is normally present in all  module archive files.  The
  update to the manifest, while preserving manifest logical
  values (attributes), can be a change to the format
  of these values, can be a change to white-space characters,
  and can be a change to line end characters.  The update to
  the manifest can change the size of the manifest file.
  The problem was noticed using the administrative scripting
  client, using the "-jython" option, and using the command:
  AdminApplication.addUpdateSingleModuleFileToAnAppWithUpdateComma
  nd
  When noted, the problem symptom was a change of the size of the
  manifest file of the module which was updated.  The manifest
  size changed because the line end characters within the
  manifest were changed.  The line end characters were changed
  from from 0x0a 0x0a (two bytes) to 0x0d 0x0a 0x0d 0x0a (four
  bytes).
  The problem may not be visible when viewing a manifest file,
  depending on how the manifest file is viewed.  Generally, a
  binary or hexadecimal view of a manifest file is
  necessary to see what line ending characters are present.
  The problem is specific to module update processing.  The
  problem does not occur during the initial deployment of an
  application.
  The update to the manifest file does not prevent normal
  functioning of the application server, but may cause problems
  for external tools which require that the manifest file not be
  changed.  The manifest remains valid, and has the same
  logical values (attributes) as before the update.
  

Problem conclusion

• The problem was fixed by adding steps to the processing of
  module file manifest files during update processing.  The added
  steps make a note of the original bytes of a manifest file
  and ensure that these bytes are used to write the manifest
  file when no logical values (attributes) within the manifest
  are changed.
  
  There is no work-around to the problem.  Installation of an
  ifix or of a service level which includes the fix, together
  with either a new update of the affected module or a new
  installation of the affected application, are necessary.  The
  problem may be corrected by directly correcting the affected
  manifest files in the deployed application file sets, but,
  this is not advised because of the complexity of locating and
  updating all necessary files and because of the potential to
  adversely affect application files.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.6.  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