IDP 3.1.0 - Ldap - Operation exception encountered, reopening connection

[Koch, Ken]

Well I ‘thought’ all 3 of our IDPs were on the same version.

One of them’s version.bat shows 3.1.0. The other two show 3.0.0. Funny thing, since we upgraded all three on the same day. I can even re-run the 3.1.0 installer and it doesn’t detect an update needed.

Comparing directories between a 3.0.0 and a 3.1.0 shows that the two corrupted 3.1.0 installs still have some 3.0.0 JAR files leftover. There’s definitely a few other files that are different in core directories.

I wonder if the 3.1.0 installer bombed but didn’t error out? I’ll ask the guy that ran it when he gets in. We’ll also add the verison.bat check to our process at the tail end.


-Ken

From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Daniel Fisher
Sent: Thursday, March 26, 2015 9:41 PM
To: Shib Users
Subject: Re: IDP 3.1.0 - Ldap - Operation exception encountered, reopening connection

On Thu, Mar 26, 2015 at 4:44 PM, Koch, Ken <ken at wustl.edu<mailto:ken at wustl.edu>> wrote:
2015-03-26 15:18:23,722 - WARN [org.ldaptive.AbstractOperation$ReopenOperationExceptionHandler:277] - Operation exception encountered, reopening connection
2015-03-26 15:18:23,722 - ERROR [org.ldaptive.AbstractOperation$ReopenOperationExceptionHandler:139] - unable to handle operation exception
org.ldaptive.provider.ConnectionException: javax.naming.CommunicationException: <hostname>:636 [Root exception is java.lang.NullPointerException: Thread local SslConfig has not been set]
                at org.ldaptive.provider.jndi.JndiConnectionFactory.createInternal(JndiConnectionFactory.java:86)
Caused by: javax.naming.CommunicationException: <hostname>:636
                at com.sun.jndi.ldap.Connection.<init>(Unknown Source)
Caused by: java.lang.NullPointerException: Thread local SslConfig has not been set
                at org.ldaptive.ssl.ThreadLocalTLSSocketFactory.getDefault(ThreadLocalTLSSocketFactory.java:61)
2015-03-26 15:18:23,738 - WARN [org.ldaptive.pool.BlockingConnectionPool:808] - connection failed validation: org.ldaptive.pool.AbstractConnectionPool$DefaultPooledConnectionProxy at 6590f23<mailto:org.ldaptive.pool.AbstractConnectionPool$DefaultPooledConnectionProxy at 6590f23>

This looks like this bug: https://github.com/vt-middleware/ldaptive/issues/24
Which was fixed in ldaptive 1.0.6 and shipped with IDP v3.1.0.
Are you certain you're running version 3.1.0?

--Daniel Fisher

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150327/440a9a17/attachment.html