IBM Support

PH19982: WASPREUPGRADE ISSUE "THE CELLCONFIGMANAGER IS A SINGLETON"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An error in the code when all profiles are being collected by
    WASPreUpgrade instead of specifying a profile with -profileName
    -
    The error is
    java.lang.Exception: Coding Error: The CellConfigManager is a
    singleton and was
    
    already created. Use getCellConfigData() to obtain a reference.
    MIGR0272E: The migration function cannot complete the command."
    

Local fix

  • Run the waspreupgrade command with the -oldprofile keyword
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Configuration Migration Tools        *
    ****************************************************************
    * PROBLEM DESCRIPTION: UpgradeException involving              *
    *                      CellConfigDataManager causes            *
    *                      WASPreUpgrade to fail                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem occurs when WASPreUpgrade is invoked without
    specifying a -oldProfile parameter. In this configuration,
    WASPreUpgrade collects each profile in the target installtion
    in turn into the same backup directory. As part of the
    collection process, WASPreUpgrade creates a
    CellConfigDataManager to hold information about the cell. This
    data manager is intended to only be initialized once, but is
    not destroyed when WASPreUpgrade is finished with one profile,
    causing an exception when it tries to initialize an already
    initialized CellConfigDataManager.
    

Problem conclusion

  • Migration was adjusted to properly handle the
    CellConfigDataManager when multiple profiles are being
    collected.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.3.  For more information, see 'Recommended Updates for
    WebSphere Application Server':
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH19982

  • 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

    2019-12-05

  • Closed date

    2020-01-07

  • Last modified date

    2021-03-24

  • 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

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

Document Information

Modified date:
25 March 2021