Fixes are available
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
In some cases, WebSphere Application Server can fail to start when the Federated Repository configuration contains one or more Domino LDAP servers which are offline during the server startup process, even if the allowOperationIfReposDown="true" setting has been enabled.
Local fix
If the Domino LDAP supports the dominouid attribute, add the following entry into the wimconfig.xml within the <config:attributeConfiguration> for the Domino LDAP: <config:externalIdAttributes name="dominounid"/>
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM WebSphere Application Server * * with * * an IBM Lotus Domino Ldap server defined. * **************************************************************** * PROBLEM DESCRIPTION: In some cases, WebSphere Application * * Server can fail to start when a Domino * * LDAP server is not reachable during the * * server startup process. * **************************************************************** * RECOMMENDATION: * **************************************************************** In some cases, WebSphere Application Server can fail to start when the Federated Repository configuration contains one or more IBM Lotus Domino LDAP servers which are offline during the server startup process, even if the allowOperationIfReposDown="true" setting has been enabled.
Problem conclusion
The initialization process was fixed to allow server startup when an IBM Lotus Domino Ldap server is unreachable. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.15, 8.5.5.14, and 9.0.0.8. 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
PI92274
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-01-10
Closed date
2018-03-07
Last modified date
2018-03-07
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
R800 PSY
UP
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
03 May 2022