Every ten seconds this message is displayed in the IDP catalina.out.

This IDP doesn't have any reason to connect to the ldap store, as it is not configured as a user store on this IDP cluster.

Just curious.

<amLogEntry> 2017-06-23T14:00:07Z DEBUG NIDS Application:
Method: JNDILogEventListener.accept
Thread: JNDIReplicaRestart-cd4ba870-3b16-4d38-95e5-9af8a8d216f4
Pool Id: PL2ae3cf49-27d8-4886-b10f-09f35bbc293c:b01d463f-36cf-479f-b5bd-ce1c23258ea9, Opening pool on host: ldaps://172.16.0.91 </amLogEntry>

<amLogEntry> 2017-06-23T14:00:07Z DEBUG NIDS Application:
Method: JNDILogEventListener.accept
Thread: JNDIReplicaRestart-cd4ba870-3b16-4d38-95e5-9af8a8d216f4
Connection: cf2d0544-f436-4480-b73d-6f628ca0668e, Environment Parameters for InitialDirContext() method call:
Key: java.naming.factory.initial, Value: com.sun.jndi.ldap.LdapCtxFactory
Key: java.naming.provider.url, Value: ldaps://172.16.0.91:636
Key: com.sun.jndi.ldap.connect.timeout, Value: 0
Key: java.naming.security.principal, Value: cn=admin,o=services
Key: java.naming.security.authentication, Value: simple
Key: java.naming.security.credentials, Value: *****
Key: java.naming.security.protocol, Value: ssl
Key: java.naming.ldap.factory.socket, Value: com.novell.nidp.common.util.net.client.NIDP_SSLSoc ketFactory
</amLogEntry>

<amLogEntry> 2017-06-23T14:00:07Z DEBUG NIDS Application:
Method: JNDILogEventListener.accept
Thread: JNDIReplicaRestart-cd4ba870-3b16-4d38-95e5-9af8a8d216f4
CommunicationException: Connection: cf2d0544-f436-4480-b73d-6f628ca0668e, Attempting to create InitialDirContext for replica: DevIDV </amLogEntry>

<amLogEntry> 2017-06-23T14:00:07Z DEBUG NIDS Application:
Method: JNDILogEventListener.accept
Thread: JNDIReplicaRestart-cd4ba870-3b16-4d38-95e5-9af8a8d216f4
Exception while attempting to create ldap connection! </amLogEntry>

<amLogEntry> 2017-06-23T14:00:07Z DEBUG NIDS Application:
Method: JNDILogEventListener.accept
Thread: JNDIReplicaRestart-cd4ba870-3b16-4d38-95e5-9af8a8d216f4
Replica: Id: b01d463f-36cf-479f-b5bd-ce1c23258ea9, host: ldaps://172.16.0.91, Initiating placement onto restart thread! </amLogEntry>

<amLogEntry> 2017-06-23T14:00:07Z DEBUG NIDS Application:
Method: JNDILogEventListener.accept
Thread: JNDIReplicaRestart-cd4ba870-3b16-4d38-95e5-9af8a8d216f4
Replica: Id: b01d463f-36cf-479f-b5bd-ce1c23258ea9, host: ldaps://172.16.0.91, Already on restart thread! </amLogEntry>

<amLogEntry> 2017-06-23T14:00:07Z DEBUG NIDS Application:
Method: JNDILogEventListener.accept
Thread: JNDIReplicaRestart-cd4ba870-3b16-4d38-95e5-9af8a8d216f4
Replica ldaps://172.16.0.91 restart failed! Will try again after 10000 milliseconds! </amLogEntry>

<amLogEntry> 2017-06-23T14:00:17Z DEBUG NIDS Application:
Method: JNDILogEventListener.accept
Thread: JNDIReplicaRestart-cd4ba870-3b16-4d38-95e5-9af8a8d216f4
Pool Id: PL2ae3cf49-27d8-4886-b10f-09f35bbc293c:b01d463f-36cf-479f-b5bd-ce1c23258ea9, Opening pool on host: ldaps://172.16.0.91 </amLogEntry>

<amLogEntry> 2017-06-23T14:00:17Z DEBUG NIDS Application:
Method: JNDILogEventListener.accept
Thread: JNDIReplicaRestart-cd4ba870-3b16-4d38-95e5-9af8a8d216f4
Connection: dabdbfba-00c6-455e-94c5-a8a02c82acfe, Environment Parameters for InitialDirContext() method call:
Key: java.naming.factory.initial, Value: com.sun.jndi.ldap.LdapCtxFactory
Key: java.naming.provider.url, Value: ldaps://172.16.0.91:636
Key: com.sun.jndi.ldap.connect.timeout, Value: 0
Key: java.naming.security.principal, Value: cn=admin,o=services
Key: java.naming.security.authentication, Value: simple
Key: java.naming.security.credentials, Value: *****
Key: java.naming.security.protocol, Value: ssl
Key: java.naming.ldap.factory.socket, Value: com.novell.nidp.common.util.net.client.NIDP_SSLSoc ketFactory
</amLogEntry>