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 Tue, 21 Sep 2010 17:54:32 GMT


Emmanuel Lecharny commented on DIRAPI-30:

Seems like the issue is due to the fact that we don't wait until the connection is fully closed
before starting a new connection :

- start connection
- send a bindRequest ( the futureMaps is being fed with <messageId, bindFuture> )
- received the bindResponse
- get the bindFuture from the futureMaps, then close the session
- start another connection
- send a bindRequest ( the futureMaps is being fed with <messageId, bindFuture> )
- the sessionClosed() event is *now* being received, and it does :
    public void sessionClosed( IoSession session ) throws Exception

which clear the futureMaps
- then the messageReceived() event is being processed, and tries to read the bindFuture from
the map, but as it has been cleaned, we don't find anything => bug !

> 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