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

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

The problem seems to be on the client side. The last packet I see being sent 
from the server is a SASL bind Response, containing :
30 43 (LdapMessage)
  02 01 01 (Message Nb 1)
  61 3e (BindResponse)
    0a 01 0e (SASL bind in progress)
    04 00 (matchedDN)
    04 00 (errorMessage)
    87 35  (SASL credentials)
      60 33 (credentials)
        06 09 
          2a 86 48 86 f7 12 01 02 02 (OID 1.2.840.113554.1.2.2 KRB5)
          02 01 (krb5_tok_id : KRB5 GSS Wrap)
          00  00 (krb5_sgn_alg : DES MAC DS5)
          ff ff ff ff (krb5_seal_alg : none)
          13 37 1c 13 2f 2a 73 e6 (krb5_snd_seq)
          a3 ff 10  48 e2 fb c0 8e (krb5_sgn_cksum)
          70 f6 26 2c 2c 76 c4 03 (krb5confounder)


(Those bytes have been read with wireshark, so they actually have been sent by 
the server)

Let's see what's wrong on the client side...


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

Reply via email to