Issues with LDAP and Sametime/Domino 8.0.2

Been running into issues lately with Sametime and LDAP.  The Sametime is version 8.0.2 running on Domino of the same version.  The issue occurs whenever the LDAP server gets rebooted.  The LDAP service on the Domino server isn't able to re-establish the connection to the LDAP server when it comes back up.  Restarting the LDAP service on Domino doesn't re-establish the connection either.  To solve the issue, the entire Domino service needs to be restarted.

This can't be the norm for working with LDAP.  Is there something I am missing that will resolve the issue?  I will keep investigating.

<< Previous Document / Next Document >>
  • 1) these aren’t on the same box right? - Carl Tyler
    Created 5/11/2009 11:49:14 PM email | website

    Your LDAP server and Sametime server aren't on the same domino server are they?

  • 2) Sametime/LDAP - Marie Scott
    Created 5/12/2009 6:56:36 AM email | website

    We're not connecting to a Domino LDAP but I have these in the sametime.ini in the [DIRECTORY] section:

    ST_DB_LDAP_KEEPALIVE_INTERVAL=1

    ST_DB_LDAP_RESPRAY_INTERVAL=5

    ST_DB_LDAP_PENDING_LOW=30

    ST_DB_LDAP_PENDING_MAX=60

  • 3) Re: Sametime/LDAP - Sean Burgess
    Created 5/13/2009 9:13:23 AM email | website

    @1 No, the LDAP server is a Tivoli Directory Server running on zLinux. They take it down every other weekend for backups.

    @2 Not sure any of those will help, but I will check and see what my INI looks like. The connection only gets re-established by doing a Restart Server.

  • 4) Re: Sametime/LDAP - Franck Hoo
    Created 9/29/2009 3:47:44 PM email |

    I experienced the same behaviour a while ago.

    The DA was working well after that the LDAP was restarted.

    The ST Community Service was OK and people could login for chatting.

    The Meeting Service did not allow people to reconnect and the only workaround that I found was to stop and start the HTTP task (not restart).

  • 5) Don’t forget DB2 and also the Gateway. - Hinshaw
    Created 12/11/2010 8:08:08 PM email | website

    Don't forget DB2 and also the Gateway. If you want SIP/SSL you then need the WAS Proxy component. At least in 8.5 the port conflict issues are resolved.


Discussion for this entry is now closed.