Fixes are available
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
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
Document Information
Modified date:
04 May 2022