Fixes are available
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
On Websphere Application Server v7.0, when profile creation failed due to incorrect hostname configuration: Operating System "hostname" is configured on machine, but there is no entry for this hostname in file "/etc/hosts". The install log in <WAS_HOME>/install/logs directory still shows a success message: INSTCONFSUCCESS. This is mis-leading message, instead should be INSTCONFPARTIALSUCCESS as profile creation failed.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users who install IBM WebSphere Application * * Server and create profiles during the * * install process on the system which meet * * the following two conditions: * * 1) Operating System "hostname" is * * configured on the machine; * * 2) There is no entry for this hostname in * * the configuration file "/etc/host". * **************************************************************** * PROBLEM DESCRIPTION: When installing Application * * Server ¯ ’profile creation will fail, * but the installer reports * * "INSTCONFSUCCESS" in log. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere Application Server Installer invokes Profile Management Tools (PMT) for profile generation, and checks the return code from PMT to understand if the operation was successful or not. In this very limited situation PMT encountered an exception and the profile was not created, however PMT returns zero as a return code to the installer. That's why installer thinks profile creation was successful.
Problem conclusion
Besides the return code, the installer will also check "Standard Output" from PMT to understand if profile creation was successful or not. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.19. The change will take effect when customer s build a Customized Installation Package (CIP) via Install Factory (IF), using WebSphere Application Server plus the fix pack which contains this fix. 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
PM33510
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-02-24
Closed date
2011-04-04
Last modified date
2011-04-04
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
R700 PSY
UP
Document Information
Modified date:
27 October 2021