Fixes are available
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
Migrating from previous version to WebSphere Application Server V8.0 and then migrating to WebSphere Application Server V8.5.5 causes server startup failure. By default the profile creation places the jsf-MyFaces.xml into the server's wsBundleMetadata directory that is WAS_HOME/profiles/profile_name/servers/server_name/configuration /wsBundleMetadata/ If the profile was migrated to v8.0 from some previous version of WebSphere Application Server the default back then was to use the Sun RI version of JavaServer Faces (JSF). So that migration set the SunRI into the server's v8.0 wsBundleMetadata directory. Now with another migration to 8.5.5, it is copying the migrated SunRI version into the wsBundleMetadata directory along with the MyFaces (default) version of the file.
Local fix
Remove the jsf-MyFaces.xml from the server1's wsBundleMetadata location that is WAS_HOME/profiles/profile_name/servers/server_name/configuration /wsBundleMetadata/ Run ./osgiCfgInit.sh -servers server_name from the WAS_HOME/profiles/profile_name/bin directory then start the server.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Incorrect JSF xml file exists in * * server's wsBundleMetadata directory * * after migration. * **************************************************************** * RECOMMENDATION: * **************************************************************** Profile creation automatically inserts the default JSF, and migration only looks for one JSF, always finding the default.
Problem conclusion
Updated code to look for correct JSF in server.xml instead of wsBundleMetadata directory. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.3. 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
PI13020
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-03-04
Closed date
2014-05-22
Last modified date
2014-05-22
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