Print

Presence Service exceptions

One of the following exception has occurred in the Presence Services.

  • During initialization, if the Sametime server is not running the Presence Services will continue to attempt to connect to the Sametime server until it becomes available.

    jvm 1    | INFO: The presence service started.
    jvm 1    | Mar 26, 2008 10:28:11 AM 
    com.lotus.sametime.telephonymanager.config.STConfigurationReader loggedOut
    jvm 1    | WARNING: warn.disconnect.sametime 80000207 ST_CONNECT_HOST_UNREACHABLE
    jvm 1    | Mar 26, 2008 10:29:12 AM 
    com.lotus.sametime.telephonymanager.config.STConfigurationReader loggedOut
    jvm 1    | WARNING: warn.disconnect.sametime 80000207 ST_CONNECT_HOST_UNREACHABLE
    jvm 1    | Mar 26, 2008 10:30:13 AM 
    com.lotus.sametime.telephonymanager.config.STConfigurationReader loggedOut
    jvm 1    | WARNING: warn.disconnect.sametime 80000207 ST_CONNECT_HOST_UNREACHABLE
    jvm 1    | Mar 26, 2008 10:31:14 AM 
    com.lotus.sametime.telephonymanager.config.STConfigurationReader loggedOut
    jvm 1    | WARNING: warn.disconnect.sametime 80000207 ST_CONNECT_HOST_UNREACHABLE
    jvm 1    | Mar 26, 2008 10:32:15 AM 
    com.lotus.sametime.telephonymanager.config.STConfigurationReader loggedOut
    jvm 1    | WARNING: warn.disconnect.sametime 80000207 ST_CONNECT_HOST_UNREACHABLE
    jvm 1    | Mar 26, 2008 10:33:16 AM 
    com.lotus.sametime.telephonymanager.config.STConfigurationReader loggedOut
    jvm 1    | WARNING: warn.disconnect.sametime 80000207 ST_CONNECT_HOST_UNREACHABLE
    jvm 1    | Mar 26, 2008 10:34:16 AM 
    com.lotus.sametime.telephonymanager.config.STConfigurationReader onConfigChanged
    jvm 1    | INFO: number of servers in the community is 1
    jvm 1    | Mar 26, 2008 10:34:16 AM 
    com.lotus.sametime.telephonymanager.config.STConfigurationReader readServerDetails
    jvm 1    | INFO: name: CN=stdev/O=aes, URL: stdevel.dr.avaya.com
    jvm 1    | Mar 26, 2008 10:34:16 AM 
    com.lotus.sametime.telephonymanager. Telephony AdapterImpl resolverIsReady
    jvm 1    | INFO: Community connected
    jvm 1    | Mar 26, 2008 10:34:16 AM 
    com.avaya.sametime.presence.listeners.SametimeListener communityAvailable
    jvm 1    | INFO: Sametime community is available.  Adding monitors.
    
  • After initialization, if the Sametime server becomes unavailable, the Presence Services will continue to attempt to reconnect until it becomes available.
    jvm 1    | Mar 26, 2008 10:42:26 AM 
    com.avaya.sametime.presence.listeners.SametimeListener communityNotAvailable
    jvm 1    | INFO: Sametime community is unavailable.
    jvm 1    | Mar 26, 2008 10:42:26 AM 
    com.lotus.sametime.telephonymanager.cluster.ClusterManager serverLoggedOut
    jvm 1    | WARNING: warn.server.disconnected
    jvm 1    | Mar 26, 2008 10:42:26 AM 
    com.lotus.sametime.telephonymanager. Telephony AdapterImpl serverLoggedOut
    jvm 1    | INFO: Server stdevel.dr.avaya.comloggedout. handling data
    jvm 1    | Mar 26, 2008 10:42:26 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING: reason = -2147483623
    jvm 1    | Mar 26, 2008 10:43:27 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING: reason = -2147483129
    jvm 1    | Mar 26, 2008 10:44:28 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING: reason = -2147483129
    jvm 1    | Mar 26, 2008 10:45:29 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING: reason = -2147483129
    jvm 1    | Mar 26, 2008 10:46:29 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING: reason = -2147483129
    jvm 1    | Mar 26, 2008 10:47:31 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING: reason = -2147483129
    jvm 1    | Mar 26, 2008 10:48:31 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING: reason = -2147483129
    jvm 1    | Mar 26, 2008 10:49:32 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING: reason = -2147483129
    jvm 1    | Mar 26, 2008 10:50:33 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING: reason = -2147483129
    jvm 1    | Mar 26, 2008 10:51:34 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING: reason = -2147483129
    jvm 1    | Mar 26, 2008 10:57:40 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING: reason = -2147483129
    jvm 1    | Mar 26, 2008 10:58:41 AM 
    com.lotus.sametime.telephonymanager.cluster.ServerManager loggedOut
    jvm 1    | WARNING
    
  • During initialization, when the Presence Services is telling the Sametime server that it wants to be notified of status changes for particular users, and an error mentioned above is logged. It indicates that there are duplicate users in the customer's enterprise directory. Domino (the container in which the Sametime server runs) may do case insensitive comparisons of names, so if you have two LDAP connections and the DN “cn=john doe,o=aes” exists in one LDAP store and the DN “cn=John Doe,o=aes” exists in the other LDAP store, you will see this error. The reason the error occurs is that the Sametime server does not have a way of distinguishing one user from the other. The solution to this is to ensure that the names in the enterprise directory are unique.

  • During initialization, when the Presence Services is registering with the Sametime server to be notified of status changes for particular users, and an error mentioned above is logged. This error may be seen if the Sametime LDAP search criteria is too broad. For instance, the default search filter for resolving person names in the Community Server at LDAP Directory > Searching is (cn=%s*). With this criteria, the Sametime server is unable to distinguish between the DN cn=johndoe and the DN cn=johndoe1. The asterisk operates as a wildcard that matches anything after the DN pattern provided to the Sametime Community Server. Once again, the solution is to ensure that the names in the enterprise directory are unique. IBM has suggested another workaround to this particular issue is to remove the asterisk from the search criteria, such that the configuration is (cn=%s).