[
https://issues.apache.org/jira/browse/DIRAPI-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912770#action_12912770
]
Emmanuel Lecharny commented on DIRAPI-30:
-----------------------------------------
This is really strange. I get an error after some iterations (as expected,,
hmmm), and as I added some logs, here is what I get :
...
try 576
SERVER : SASL bind request : BindRequest
Version : '3'
Name : 'uid=hnelson,ou=users,dc=example,dc=com'
Sasl credentials
Mechanism :'GSSAPI'
Credentials : (omitted-for-safety)
SERVER : SASL bind response challenge: BindResponse
Ldap Result
Result code : (SASL_BIND_IN_PROGRESS) saslBindInProgress -- new
Matched DN : 'null'
Error message : 'null'
Server sasl credentials : ''
CLIENT : ----------------> response = BindResponse
Ldap Result
Result code : (SASL_BIND_IN_PROGRESS) saslBindInProgress -- new
Matched DN : ''
Error message : ''
Server sasl credentials : ''
SERVER : SASL bind request : BindRequest
Version : '3'
Name : 'uid=hnelson,ou=users,dc=example,dc=com'
Sasl credentials
Mechanism :'GSSAPI'
Credentials : (omitted-for-safety)
SERVER : SASL bind response challenge: BindResponse
Ldap Result
Result code : (SASL_BIND_IN_PROGRESS) saslBindInProgress -- new
Matched DN : 'null'
Error message : 'null'
Server sasl credentials : '0x60 0x33 0x06 0x09 0x2A 0x86 0x48 0x86 0xF7
0x12 0x01 0x02 0x02 0x02 0x01 0x00 0x00 0xFF 0xFF 0xFF 0xFF 0xFD 0x59 0x76 0xBA
0xEB 0x4D 0x0A 0x17 0xCF 0x09 0x3C 0xF6 0x3D 0x70 0x8D 0x7B 0xC7 0xCE 0x13 0xA5
0x9E 0x05 0xC9 0x77 0x07 0x01 0x00 0x00 0x04 0x04 0x04 0x04 '
and we never get the message on the client side. Now, the problem is to
determinate if the problem is on the encoding part, the decoding part of
somewhere deep in MINA.
> 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.
