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

[Klingenstein, Nate]

> It's warn because the validator isn't working as it should, but it does reopen the connections.

I expect that to be something I got wrong, but I have no customization of the pool nor validation query yet.

> I'm not clear on which 'null' is making you skittish.

org.ldaptive.OperationException: javax.naming.CommunicationException: Connection reset [Root exception is java.net.SocketException: Connection reset]; remaining name ''

It's literally and completely null.  That isn’t just excerpted for privacy.  I suspect that's a hint to misconfiguration here.  We’re only using this for authentication now.

> 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.

I could also expect the behavior to change once this is under meaningful load, right?  That will be the first debugging step now that I asked about the local network architecture.
We’re forwarding communications at layer 4, so only the IdP and directory are likely culprits.  Running this under load is going to be the next step.