IBM Support

PI13020: MIGRATION HANDLING THE SERVER'S JSF DATA CAUSES SERVER STARTUP FAILURE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Migrating from previous version to WebSphere Application
    Server V8.0 and then migrating to WebSphere Application Server
    V8.5.5 causes server startup failure.
    
    By default the profile creation places the jsf-MyFaces.xml into
    the server's wsBundleMetadata directory that is
    WAS_HOME/profiles/profile_name/servers/server_name/configuration
    /wsBundleMetadata/
    
    If the profile was migrated to v8.0 from some previous version
    of WebSphere Application Server the default back then was to
    use the Sun RI version of JavaServer Faces (JSF). So that
    migration set the SunRI into the server's v8.0
    wsBundleMetadata directory.
    
    Now with another migration to 8.5.5, it is copying the migrated
    SunRI version into the wsBundleMetadata directory along with
    the MyFaces (default) version of the file.
    

Local fix

  • Remove the jsf-MyFaces.xml from the server1's wsBundleMetadata
    location that is
    WAS_HOME/profiles/profile_name/servers/server_name/configuration
    /wsBundleMetadata/
    Run ./osgiCfgInit.sh -servers server_name from the
    WAS_HOME/profiles/profile_name/bin directory then start the
    server.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect JSF xml file exists in        *
    *                      server's wsBundleMetadata directory     *
    *                      after migration.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Profile creation automatically inserts the default JSF, and
    migration only looks for one JSF, always finding the default.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI13020

  • 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-03-04

  • Closed date

    2014-05-22

  • Last modified date

    2014-05-22

  • 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