PI42186: APPLICATION DEPLOYMENT DOES NOT PRESERVE SIGNATURES OF FRAGMENT JAR FILES.

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

• When exporting an application which contains web module
  fragment JAR files, the signatures of the fragment JAR files
  may not be  preserved.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Application deployment changes the      *
  *                      signatures of web module fragment JAR   *
  *                      files.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Web module files include fragment JAR files.  The write of
  fragment JAR files during application deployment can change
  the signature of these fragment JAR files.  A change of the
  signature of a fragment JAR file is detected as a problem by
  tooling used to verify JAR file signatures.
  

Problem conclusion

• For a single fragment JAR file, a change would occur to the
  signature of the JAR file because the write of the JAR file
  recreated the file from the entries of an initial JAR file.
  Recreation of the JAR file from entries was necessary
  because annotations processing could add a new entry
  containing annotations metadata to the JAR file.
  
  The problem was resolved by a code update which causes
  the added entry to be ignored when writing the fragment JAR
  file. That enables the write to directly copy an initial JAR
  file. The write of a direct copy preserves the signature of
  the JAR file.
  
  That generated metadata is not written for the fragment JAR
  file is not a performance problem.  The save of the generated
  metadata for the JAR file is unnecessary because the generated
  metadata is merged into the generated metadata of the
  enclosing web module, and because after application
  deployment only the generated metadata of the enclosing web
  module is needed.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.7.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP