directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Ayyagari (JIRA)" <>
Subject [jira] Updated: (DIRAPI-30) Sporadic NullPointerException during SASL bind
Date Tue, 21 Sep 2010 18:39:33 GMT


Kiran Ayyagari updated DIRAPI-30:

    Attachment: dirapi30.patch

Looks like a reused bind request message ID while doing the SASL bind negotiation is causing
the issue here.
I have tried with a fix, which increments the bind request message ID during SASL negotiation
and the test passes.
However the fix increments the message id several times from what user sees as a single operation
(i.e bind)

Note: apply the patch from within the ldap-client-api module

> 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
>         Attachments: dirapi30.patch
> 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