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: (DIRSERVER-810) ldap_search_s hangs
Date Wed, 03 Jan 2007 13:06:27 GMT

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

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

Damn ! The evil NPE strik back !! (Ok, as expected ...)

Waiting for a better log, when you will have installed a new server build from 1.0-trunks,
then.

What you can do is trying this request with a different browser when the server is suppose
to hang, and also try to do another request when the serveur is supposed to be hang to see
if it's not a pb with the PDU length ( what I suspect is that when trying to decode this request,
the decoder is waiting for more bytes so wait ad vitam aeternam ...) I gonna try to implement
the decoding of this PDU as a test case just to check.

> 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.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: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message