IBM Support

PI77392: INCORRECT GENERATION OF IBM-METADATA.XML WHEN DEPLOYING WITH PRE-GENERATED MERGED DESCRIPTORS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When deploying an application which contains pre-generated
    merged deployment descriptors, annotations processing steps can
    incorrectly update ibm-metadata.xml, resulting in the file
    having incomplete data.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deployment of applications with         *
    *                      pre-generated IBM metadata writes       *
    *                      incomplete metadata.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When deploying an application which has pre-generated IBM
    metadata (META-INF/ibm-metadata.xml for EJB JAR
    files; WEB-INF/ibm-metadata.xml for WAR files), the
    pre-generated data is not always processed correctly.  That
    can result in the deployment writing incomplete metadata.
    Pre-generated metadata consists of the files
    META-INF/application_merged.xml,
    META-INF/ejb-jar_merged.xml, META-INF/ibm-metadata.xml,
    META-INF/application-client_merged.xml,
    META-INF/ra_merged.xml, WEB-INF/web_merged.xml, and
    WEB-INF/ibm-metadata.xml.  These files are present in
    application and module archives (EAR, JAR, WAR, and RAR
    files).  The pre-generated files are specific to the IBM
    WebSphere Application Server, and are not used by other
    application server implementations.
    Normally, pre-generated metadata is not present when deploying
    applications, and, the IBM recommendation is to remove any
    pre-generated metadata from an application before deploying the
    application.  The problem of this APAR will not occur if
    pre-generated metadata is removed prior to application
    deployment.
    Removal of pre-generated metadata is always necessary if any
    modifications were made to the application and the
    modifications introduce new metadata.  New metadata is, for
    example, new occurrences of JavaEE annotations such as
    @WebServlet and @EJB.
    However, occasionally, a deployment of a migrated application
    will contain metadata from the earlier deployment.  The
    problem of this APAR most typically occurs for the deployment
    of a migrated application.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI77392

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-28

  • Closed date

    2017-07-25

  • Last modified date

    2017-07-25

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021