directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRAPI-30) Sporadic NullPointerException during SASL bind
Date Tue, 21 Sep 2010 12:51:34 GMT

    [ https://issues.apache.org/jira/browse/DIRAPI-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912951#action_12912951
] 

Emmanuel Lecharny commented on DIRAPI-30:
-----------------------------------------

Not necessarilly a MINA bug, but may be a pb with the way we use MINA. Typically, we have
a BindResponse which is not completely decoded, but we don't have the remaining bytes yet.

I may have badly handled split messages in the client (if the message is received in more
than one piece).

I will investigate this. Hopefully, we can get it working soon.

> Sporadic NullPointerException during SASL bind
> ----------------------------------------------
>
>                 Key: DIRAPI-30
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-30
>             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
Mac.
> 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 org.apache.directory.ldap.client.api.LdapNetworkConnection.bindSasl(LdapNetworkConnection.java:3534)
> 	at org.apache.directory.ldap.client.api.LdapNetworkConnection.bindSasl(LdapNetworkConnection.java:3437)
> 	at org.apache.directory.ldap.client.api.LdapNetworkConnection.bindDigestMd5(LdapNetworkConnection.java:1213)
> 	at org.apache.directory.ldap.client.api.LdapNetworkConnection.bindDigestMd5(LdapNetworkConnection.java:1239)
> 	at org.apache.directory.ldap.client.api.LdapNetworkConnection.bindDigestMd5(LdapNetworkConnection.java:1192)
> 	at org.apache.directory.server.operations.bind.SaslBindIT.testSequentialBinds(SaslBindIT.java:439)
> 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.


Mime
View raw message