IBM Support

PI92274: Server fails to start when Domino Ldap server is not reachable

Subscribe

You can track all active APARs for this component.

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

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI92274

Modified date: 07 March 2018


Translate this page: