directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-810) ldap_search_s hangs
Date Wed, 03 Jan 2007 15:25:27 GMT


Emmanuel Lecharny commented on DIRSERVER-810:

No, I have just tested the last PDU. The rationnal is that if a PDU is incorrect, you will
get an error (and you don't have error so far), or if it's incomplete, then the server will
wait forever for the missing bytes, until the socket is closed by either the client or a timeout
happen. So far, the last PDU is correct and complete. 

I think there is something wrong elswhere, but to be able to analyse it, what I need is :
- a full DEBUG trace of the server with the offending sequence (trying to limit other interraction
to a bare minimum, because traces will be huge)
- all the schema and data to be able to debug the server, as far as I can reproduce the problem
on my machine and if the data are not confidential.

It's up to you...

I engage you to connect on irc (, channel #directory-dev) if you want to discuss
further, or have any question which need more interactivity. i'll be connected till 8pm, CEST
( I think we are almost on the same timezone)

> ldap_search_s hangs 
> --------------------
>                 Key: DIRSERVER-810
>                 URL:
>             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.bin, DIRSERVER-810.log-1.txt,
DIRSERVER-810.pgina.log-1.txt, DIRSERVER-810.server.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:
For more information on JIRA, see:


View raw message