Issue Details (XML | Word | Printable)

Key: DIRSERVER-623
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Endi S. Dewata
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Directory ApacheDS

Incorrect time limit unit

Created: 25/May/06 03:41 AM   Updated: 04/Oct/06 04:58 PM
Return to search
Component/s: None
Affects Version/s: 1.0-RC3
Fix Version/s: None

Time Tracking:
Not Specified

Resolution Date: 30/Jul/06 06:15 PM


 Description  « Hide
The time limit in the search request is incorrectly treated as milliseconds. According to RFC 2251 the time limit should be in seconds. The following example is done using OpenLDAP's command line tool:

  ldapsearch -h localhost -p 10389 -D uid=admin,ou=system -w secret -b "dc=example,dc=com" -l 100

The -l 100 parameter indicates that the time limit is set to 100 seconds. However, the search operation stops in less than a second with error message "Time limit exceeded". Some other LDAP client (e.g. Softerra) might specify a time limit by default, so it will affect the results.

This could be the cause of the problem: in SearchHandler.java:82, the time limit is being passed directly from SearchRequest to SearchControls. According to the documents in the code, the time limit in SearchRequest is in seconds, but the time limit in SearchControls is in milliseconds, so it should have been multiplied by 1000.


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no subversion log entries for this issue yet.