Fixes are available
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.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
A liberty server or app client with application security and remote EJBs enabled will prevent all applications from starting until SSL and a UserRegistry are completely configured. After 10 seconds an error message will be logged explaining the situation.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile - SSL * **************************************************************** * PROBLEM DESCRIPTION: If the appSecurity feature is installed * * no application will start unless SSL * * and a UserRegistry are configured * * correctly. * **************************************************************** * RECOMMENDATION: * **************************************************************** A liberty profile server or app client with application security and remote EJBs enabled will prevent all applications from starting until SSL and a UserRegistry are completely configured. After 10 seconds an error message will be logged explaining the situation.
Problem conclusion
On a Liberty profile server, all applications will start immediately. Remote EJBs will be bound in naming and become available for use after the ORB starts. EJB references will fail before the ORB starts and start working after it starts. The application client container will wait up to 5 seconds for the ORB to start and then start the client application; there is no timeout message for this. After a wait of 10 seconds, if the ORB has not started successfully there will be an error message indicating what is wrong and needs to be configured. This message currently indicates the applications have not started, which is inaccurate. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.7. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Configure SSL completely and an appropriate UserRegistry so the ORB can start. This is always required for the ORB to start; if you are not using remote ejbs in the server or application client or the global jndi context in the application client then you do not need the ORB to start.
Comments
APAR Information
APAR number
PI47351
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-08-24
Closed date
2015-08-24
Last modified date
2015-08-24
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:
28 April 2022