IBM Support

PI11257: DURING MIGRATION WASPOSTUPGRADE FAILS WITH FILENOTFOUND EXCEPTION WHEN PROCESSING APPLICATION MIGRATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the WASPostUpgrade moves the application from the backup
    directory to the target profile's installableApps folder, it
    does not fully expand all archives in the ear file.
    During migration WASPostUpgrade processing fails with messages
    similar to:
    MIGR0215W: The migration function cannot copy the file and open
    the destination file
    /opt/WebSphere/AppServer/profiles/dmgr/installableApps/My_applic
    ation.
    ear/xyzService.war/WEB-INF/lib/spring-web-3.2.4.RELEASE.jar/META
    -
    INF/web-fragment.xml.
    MIGR0215W: The migration function cannot copy the file and open
    the destination file
    /opt/WebSphere/AppServer/profiles/dmgr/installableApps/abc_
    application.ear/abc123-ejb-8.0.4.17.jar/META-INF/ibm-ejb-
    jar-bnd.xmi.
    java.io.IOException
    MIGR0286E: The migration failed to complete.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Migration Tools who are migrating    *
    *                  an application with a web-fragment.xml      *
    ****************************************************************
    * PROBLEM DESCRIPTION: WASPostUpgrade fails when it cannot     *
    *                      copy a web-fragment.xml file.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Migration does not expand archives in the application .ear
    file. Later when migration tries to copy the web-fragment.xml
    file, it is still inside the archive and therefore cannot be
    found and an exception is thrown causing WASPostUpgrade to
    fail.
    

Problem conclusion

  • Adjusted the WASPostUpgrade code to not recurse into
    directories belonging to archives in .war modules, as these
    were not expanded to make their files visible.  The
    web-fragment.xml file will be extracted later when the
    application is deployed.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.2.  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

    PI11257

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-10

  • Closed date

    2014-02-28

  • Last modified date

    2014-02-28

  • 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

[{"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.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022