directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRAPI-30) Sporadic NullPointerException during SASL bind
Date Mon, 20 Sep 2010 21:07:33 GMT


Emmanuel Lecharny commented on DIRAPI-30:

I checked the code two days ago, and the NPE is due to the fact that the response is null
when  the timeout is reached.

We have first to handle this case on the client side, to avoid the NPE, and also to determinate
why we wait such a long time we get a timeout instead of a response.

Thanks for the test, I'll investigate it.

> Sporadic NullPointerException during SASL bind
> ----------------------------------------------
>                 Key: DIRAPI-30
>                 URL:
>             Project: Directory client API
>          Issue Type: Bug
>    Affects Versions: 0.2.0
>            Reporter: Stefan Seelmann
>             Fix For: 0.2.0
> There is a sporadic NullPointerException in the SaslBindIT tests. First, it didn't occur
on my Mac, but on Linux and Windows CI builds. Now I created a test that binds 1000 times
(sequential) with CRAM-MD5, Digest-MD5 and GSSAPI, and I can reproduce the exception on my
> Most time the exception occurs during a GSSAPI bind, but also sometimes during a Digest-MD5
for Cram-MD5 SASL bind.
> Here is the thrown exception:
> java.lang.NullPointerException
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> Before the exception is thrown the test hangs for some time. The BindFuture then times
out and returns null. Is that a problem with available resources?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message