Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Fri, 9 Jun 2017 00:01:03 +0000 (UTC)
From: "Hal Deadman (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.12863093.1441899559000.34240.1496966463294@Atlassian.JIRA>
In-Reply-To: <JIRA.12863093.1441899559000@Atlassian.JIRA>
References: <JIRA.12863093.1441899559000@Atlassian.JIRA> <JIRA.12863093.1441899559269@jira-lw-us.apache.org>
Subject: [jira] [Commented] (DIRSERVER-2091) Server Side Sort Control Broken
 in 2.0.0 M20
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 09 Jun 2017 00:01:14 -0000


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

Hal Deadman commented on DIRSERVER-2091:
----------------------------------------

The patch is in the attached logerror.txt file. I think the issue on windows is that the service is running as "local system account" and it doesn't have permission to create new files in whatever java.io.tmpdir is set to by default. If you run from the command-line it works, but not when it's running as a service. 

Apparently on windows java calls GetTempPath  to get the value for java.io.tmpdir so it should always be set to something, although it may not be writable. 

The GetTempPath function checks for the existence of environment variables in the following order and uses the first path found:

The path specified by the TMP environment variable.
The path specified by the TEMP environment variable.
The path specified by the USERPROFILE environment variable.
The Windows directory.

> Server Side Sort Control Broken in 2.0.0 M20
> --------------------------------------------
>
>                 Key: DIRSERVER-2091
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-2091
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: ldap
>    Affects Versions: 2.0.0-M20
>            Reporter: Danil Flores
>         Attachments: hunderd-users.ldif, logerror.txt, sort-result.ldif
>
>
> Given a partition with several objects with objectClass=inetOrgPerson, we want to be able to perform a search with a server-side-sort request control. 
> The following ldapsearch query was giving the correct results in ApacheDS 2.0.0 M19:
> ldapsearch -H ldap://localhost:10389 -x -D "uid=admin,ou=system" -W -b "dc=example,dc=com" -s sub -a always -z 1000 "(objectClass=inetOrgPerson)" "objectClass" -E sss=-cn:2.5.13.2
> However in ApacheDS 2.0.0 M20, we get the following error upon running the same query against a similar data set:
> # search result
> search: 2
> result: 54 Loop detected
> text: LOOP_DETECT: failed for MessageType : SEARCH_REQUEST
> Message ID : 2
>    
>   SearchRequest
>         baseDn : 'dc=example,dc=com'
>         filter : '(objectCla
>  ss=inetorgperson:[5])'
>         scope : whole subtree
>         typesOnly : false
>         Size Limit : 1000
>         Time Limit : no limit
>         Deref Aliases : deref Always
>         attributes : 'objectClass'
> org.apache.directory.api.ldap.model.message.SearchRequestImpl@38b18ca0SortRequestControlImpl [sortKeys=[SortKey : [cn, 2.5.13.2,reverse]]]: java.io.IOException: The system cannot find the path specified


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)