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

[Daniel Fisher]

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

> > 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.
>
>
The default search validator uses the RootDSE, which is an empty baseDN.
The fact that it's reporting an empty name is actually expected in this
case.


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

I would expect that you'll see less of these warnings under load. There
will be less connections idle and available for periodic validation.

--Daniel Fisher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170417/750d79ea/attachment.html>