org.ldaptive.OperationException java.net.SocketException: Connection reset]; remaining name ''

[Daniel Fisher]

On Fri, Apr 14, 2017 at 5:12 PM, Klingenstein, Nate <
nklingenstein at calstate.edu> wrote:

> I’ll check with the directory administrators about changing the timeout.
> We are using a new load balancer endpoint for this.  It’s not a problem,
> but we had to back out the change last time because we didn’t have 3268
> uniformly enabled(which I didn’t know about at the time and the escalation
> never reached me), which eventually exploded with dead connections taking
> the IdP with it, so management is skittish about anything involving WARN
> and LDAP with null strings.  I appreciate the sanity check.
>

It's warn because the validator isn't working as it should, but it does
reopen the connections.
Which is why you're not seeing service problems.
I'm not clear on which 'null' is making you skittish.
What I see indicates connections are being dropped, whether on the IDP
host, the directory host, or something in between you'll have to discover.

Tuning the validation period down slightly may just do the trick and save
you the investigation time.

--Daniel Fisher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170414/4eedc50f/attachment.html>