directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DIRAPI-190) Search request time limit should override connection timeout
Date Sat, 26 Apr 2014 20:48:15 GMT

     [ https://issues.apache.org/jira/browse/DIRAPI-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stefan Seelmann resolved DIRAPI-190.
------------------------------------

    Resolution: Fixed

Fixed here: http://svn.apache.org/r1590296

> Search request time limit should override connection timeout
> ------------------------------------------------------------
>
>                 Key: DIRAPI-190
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-190
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M22
>            Reporter: Stefan Seelmann
>            Assignee: Stefan Seelmann
>            Priority: Minor
>             Fix For: 1.0.0-M23
>
>
> The LdapNetworkConnection has a "timeout" property (default 30 seconds) which is used
as max time we wait for a response. For most LDAP operations this makes sense as they don't
allow to specify any time limit. 
> For search operation a time limit can be specified. But the current code still uses a
timeout smaller than the search time limit, which may lead to unexpected errors (see DIRSTUDIO-967).
Especially the case when search time limit is 0 is not handled correctly, in that case timeout
should be Long.MAX_VALUE.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message