IBM Support

PI79985: MIGRATION WITH CLONING TO V9 MIS-HANDLES THE VIRTUALHOSTS CREATING DUPLICATE ENTRIES.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The adminconsole wouldn't open due to running out of JVM memory
    Then after increasing the JVM memory, the console opened but
    then received errors when trying to start an application server
    , it complained about duplicate hosts. That's when it was
    noticed that the virtual host had over 175K entries.  After
    editing the virtualhost file, it worked fine.
    

Local fix

  • Edit the virtualhost xml manually.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Migration Tooling                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The virtualhosts.xml file is bloated    *
    *                      with invalid HostAliases during a       *
    *                      "Clone" migration.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When clone support was added it does not allow the target
    profile to use the same ports as the old profile.  Thus when
    the mapped ports of the hostaliases are added to the
    virtualhosts.xml and the old ones are not removed.
    Investigation showed that the virtualhosts.xml file was never
    processed correctly for federated nodes.  It was left up to
    the customer to manually correct this file.  Clone attempted
    to make this a bit easier but did not provided a complete
    solution.
    

Problem conclusion

  • The virtualhosts.xml file, although a cell level file, will
    continue to be processed by the Deployment Manager migration
    and now it will also be processed by the Federated node
    migrations.  This will allow proper handling of the changed
    host name and changed port settings.  Each node will only
    process its portion of the virtualhosts.xml file.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.0.5.  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

    PI79985

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-13

  • Closed date

    2017-06-08

  • Last modified date

    2017-06-08

  • 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

  • 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