Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <21436145.1167827607784.JavaMail.jira@brutus>
Date: Wed, 3 Jan 2007 04:33:27 -0800 (PST)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIRSERVER-810) ldap_search_s hangs
In-Reply-To: <18198599.1167797247501.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DIRSERVER-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461942 ] 

Emmanuel Lecharny commented on DIRSERVER-810:
---------------------------------------------

After inspection of your tcpdump, I see that the last received request  is a search request for (& ( uid=buster ) ( sbAttribute=Buy )). There is only one strange thing about it : we have a space after 'buster' and 'Buy' in the request :
30 84 00 00 00 65 
  02 01 03
  63 84 00 00 00 5c
    04 12 
      6f 75 3d 75 73 65 72 73 2c 6f 75 3d 73 79 73 74 65 6d ;; 'ou=users,ou=system'
    0a 01 01 
    0a 01 00
    02 01 00 
    02 01 1e 
    01 01 ff 
    a0 84 00 00 00 2d
      a3 84 00 00 00 0e 
        04 03 
          75 69 64
        04 07 
          62 75 73 74 65 72 20  ;; 'buster '  (with a space at the end)
      a3 84 00 00 00 13 
        04 0b 
          73 62 41 74 74 72 69 62 75 74 65 ;; sbAttribute
        04 04 
          42 75 79 20 ;; 'Buy ' (with a space at the end)
      30 84 00 00 00 00

I don't know if this space has some impact on the search (it depends on the sbAttribute type), I think it's ignored, but I just wonder why the clent send it. Another element which is a surprise is the 84 XX XX XX XX which is used to describe the length of the following bytes. Whatever, this is normally handled by the server.

At this point, I would like to know how many entries you have in the server, and if you obtain the same hang with LdapBrowser, for instance, with the same request.

Of course, some server trace will be helpfull (except that 1.0 has a bug which generate a NPE when in DEBUG mode,  so you will have to create a new installer from 1.0-trunks branch, where we have a fixed version)

> ldap_search_s hangs 
> --------------------
>
>                 Key: DIRSERVER-810
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-810
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: ldap
>    Affects Versions: 1.0
>         Environment: Client: Windows XP
> Server: Mac OS X
>            Reporter: Andrei Tchijov
>         Attachments: DIRSERVER-810.ldapSearchCompare.c, DIRSERVER-810.log-1.txt, DIRSERVER-810.pgina.log-1.txt
>
>
> I am trying to use pGINA ldapauth module against ApacheDS.  It mostly work, but there is one scenario when ldap_search_s call hangs indefinitely.  I am quite sure that ldap_search_s gets invoked and I am almost sure that it gets invoked with good parameters.  On server side, I know that none of interceptors gets invoked for this request.  I have captured packets with tcpdump and will attach results to this ticket.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira