Fixes are available
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
During a failed application deployment operation, some changed files were not cleaned up. This resulted in the "manage applications" link being presented. Following the "manage applications" link allows for the opportunity to save these changed files. This may result in a corrupted configuration. In the reported case, the issue was that an incomplete application configuration was saved in the configuration. During the deployment, the following was seen on the console: ADMA5014E: The installation of application TestApplication failed. The installation of application TestApplication failed. To work with installed applications, click the "Manage Applications" link. Clicking the link presented the following dialogue: WarningChanges have been made to your local configuration. You can: Save directly to the master configuration. Review changes before saving or discarding. An option to synchronize the configuration across multiple nodes after saving can be enabled in Preferences. WarningThe server may need to be restarted for these changes to take effect. Saving these changes corrupted the configuration.
Local fix
The workaround is to always choose to discard the changes after a failed deployment.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5 using the administrative * * console to install applications. * **************************************************************** * PROBLEM DESCRIPTION: When an application installation * * fails and all files cannot be removed * * from the workspace, the user must * * delete the workspace. * **************************************************************** * RECOMMENDATION: * **************************************************************** The user may not read the error and is directed to manage applications. They need to be directed to discard the workspace.
Problem conclusion
When the application install fails on the administrative console and files are not cleaned up from the install, the console will ONLY display a link to discard the workspace. The user MUST discard the workspace to prevent saving an invalid configuration. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.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
PI19234
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-06-03
Closed date
2014-09-25
Last modified date
2014-09-25
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
Document Information
Modified date:
28 April 2022