Fixes are available
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
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
The interim fix installer lays down certain information to tell the system to do this automatically on next start but for some reason that appears to have failed. The failure only appears to happen if you are applying the fix to a system where you have a server that has only been started once, for example: install product server start server stop install fix server start at this point you would currently need to start the server using the --clean argument. If the server had been started on more than one occasion before the ifix had been installed, the ifix would have automatically become active on the server start after application.
Local fix
Start the server more than once before the ifix is installed
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM WebSphere Application Server * * Liberty Profile applying an interim fix. * **************************************************************** * PROBLEM DESCRIPTION: An applied interim fix is not * * detected and is not available at * * runtime. * **************************************************************** * RECOMMENDATION: * **************************************************************** The server should automatically clean start after an interim fix has been installed. There are two scenarios where this fails to happen. Firstly, if the server has only been started once before the interim fix is installed then the service fingerprint folders are not created and the new interim fix is not detected. Secondly, if the interim fix applies to the server launcher then the automatic clean start happens after the old version of the server launcher has loaded.
Problem conclusion
The problem is fixed by ensuring that the necessary folders are created and that the clean start is requested prior to loading the server launcher. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Stopping the server and then starting it with the --clean argument will resolve the issue.
Comments
APAR Information
APAR number
PI06340
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-11-18
Closed date
2014-02-26
Last modified date
2014-02-26
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
WAS LIBERTY COR
Fixed component ID
5725L2900
Applicable component levels
R855 PSY
UP
Document Information
Modified date:
27 April 2022