LDAP connections Retry

[Niva Agmon]

>
> Timing out creating new connections or timing out performing operations?
>

Both (partially) –

a.       Performing operations (= resolving attributes):

Dec 20 22:50:32 xxxxx tomcat 212.77.220.109 - - [20/Dec/2017:22:50:32 -0500] "POST /idp/profile/cas/login;jsessionid=B176BEDB6686C36B7D4B98070F33060F?execution=e1s2 HTTP/1.1" 302 -

Dec 20 22:50:32 xxxxx tomcat 212.77.220.109 - - [20/Dec/2017:22:50:32 -0500] "GET /idp/js/temple.js HTTP/1.1" 304 -

Dec 20 22:50:34 xxxx.temple.edu 2017-12-20 22:50:34,634 - 212.77.220.109 - |Profile Action ValidateUsernamePasswordAgainstLDAP: Login by 'xxxxxxx' succeeded

Dec 20 22:50:37 xxxx.temple.edu 2017-12-20 22:50:37,668 - 212.77.220.109 - |Profile Action ResolveAttributes: Error resolving attributes

Dec 20 22:50:37 xxxx.temple.edu #011net.shibboleth.idp.attribute Data Connector 'myLDAP': Unable to execute LDAP search

Dec 20 22:50:37 xxxx.temple.edu #011at net.shibboleth.idp.attribute.resolver.dc.ldap.impl.LDAPDataConnector.retrieveAttributes(LDAPDataConnector.java:170)

…

Dec 20 22:50:37 xxxx.temple.edu 2017-12-20 22:50:37,668 - 212.77.220.109 - |Profile Action ResolveAttributes: Error resolving attributes

Dec 20 22:50:37 xxxx.temple.edu #011net.shibboleth.idp.attribute Data Connector 'myLDAP': Unable to execute LDAP search

….

Dec 20 22:50:37 xxxx.temple.edu #011Caused by: org.ldaptive.LdapException: javax.naming.NamingException: LDAP response read timed out, timeout used:3000ms.



b.       Creating new connections – fails partially - just realized that it works if I use ssl (port 636), but fails if we use starttls –



2017-12-21 22:24:10,493 - WARN [org.ldaptive.AbstractOperation$ReopenOperationExceptionHandler:277] - Operation exception encountered, reopening connection

2017-12-21 22:24:13,503 - ERROR [org.ldaptive.AbstractOperation$ReopenOperationExceptionHandler:139] - unable to handle operation exception

org.ldaptive.provider.ConnectionException: javax.naming.ServiceUnavailableException: np-ldapr1xxxxxx:389; socket closed

        at org.ldaptive.provider.jndi.JndiStartTLSConnectionFactory.createInternal(JndiStartTLSConnectionFactory.java:95)

Caused by: javax.naming.ServiceUnavailableException: np-ldapr1xxxxxxx:389; socket closed

        at com.sun.jndi.ldap.Connection.readReply(Connection.java:454)

2017-12-21 22:24:13,510 - WARN [net.shibboleth.idp.authn.impl.ValidateUsernamePasswordAgainstLDAP:192] - Profile Action ValidateUsernamePasswordAgainstLDAP: Login by nagmon produced exception

org.ldaptive.OperationException: javax.naming.CommunicationException: connection closed [Root exception is java.io.IOException: connection closed]; remaining name 'ou=people,dc=temple,dc=edu'

        at org.ldaptive.provider.ProviderUtils.throwOperationException(ProviderUtils.java:67)

Caused by: javax.naming.CommunicationException: connection closed

        at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2002)

Caused by: java.io.IOException: connection closed

        at com.sun.jndi.ldap.LdapClient.ensureOpen(LdapClient.java:1592)



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20171222/66aaa89d/attachment-0001.html>