IBM Support

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

Subscribe

You can track all active APARs for this component.

 

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 number

    PI42186

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-01

  • Closed date

    2015-08-17

  • Last modified date

    2015-08-17

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022