Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Wed, 7 Jun 2017 23:03:18 +0000 (UTC)
From: "Hal Deadman (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.12863093.1441899559000.23297.1496876598139@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: quoted-printable
archived-at: Wed, 07 Jun 2017 23:03:23 -0000


    [ https://issues.apache.org/jira/browse/DIRSERVER-2091?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
16041852#comment-16041852 ]=20

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

I am getting this error with some code that used to work (and works in othe=
r environment). I am running M23 on windows with Java 8. Not sure what chan=
ged, but I think it must be something in the directory because the client c=
ode used to work. I had one directory that I set up from scratch using an l=
dif backup and another server that I am trying to recover after the server =
ran out of disk space, and both are getting the error.=20

I can get the error both from a Java client using spring ldap and from ldap=
search but only I specify server side sorting and only if the filter return=
s more than one result.

This is what error looks like in ldapsearch:
# ldapsearch -H ldap://10.137.17.132:389 -E sss=3Dcn -x -D "uid=3Dadmin,ou=
=3Dsystem" -w xyz -b "ou=3Dgroups,dc=3Dexample,dc=3Dorg" -s sub  "(&(object=
Class=3DgroupOfUniqueNames)(uniqueMember=3Duid=3Doj.c,ou=3DPeople,dc=3Dexam=
ple,dc=3Dorg))" cn
# extended LDIF
#
# LDAPv3
# base <ou=3Dgroups,dc=3Dexample,dc=3Dorg> with scope subtree
# filter: (&(objectClass=3DgroupOfUniqueNames)(uniqueMember=3Duid=3Doj.c,ou=
=3DPeople,dc=3Dexample,dc=3Dorg))
# requesting: cn
# with server side sorting control
#

# search result
search: 2
result: 54 Loop detected
text: LOOP_DETECT: failed for MessageType : SEARCH_REQUEST
Message ID : 2
    S
 earchRequest
        baseDn : 'ou=3Dgroups,dc=3Dexample,dc=3Dorg'
        filter : '(&(objectClass=3Dgroupofuniquenames:[10])(uniqueMember=3D=
0.9.2342.19200300.100.1.1=3Doj.c,2.5.4.11=3Dpeople,0.9.2342.19200300.100.1.=
25=3Dexample,0.9.2342.19200300.100.1.25=3Dorg:[=E2=88=9E]))'
        scope : whole subtree
        typesOnly : false
        Size Limit : no limit
        Time Limit : no limit
        Deref Aliases : never Deref Aliases
        attributes : 'cn'
org.apache.directory.api.ldap.model.message.SearchRequestImpl@4e0d0648SortR=
equestControlImpl [sortKeys=3D[SortKey : [cn]]]: java.io.IOException: The s=
ystem cannot find the path specified


In java I get same message more or less and it refers to  java.io.IOExcepti=
on: The system cannot find the path specified

I don't get any errors on the server in the apacheds.log but I might need t=
o turn up the logging.=20

This is the same ldapsearch without the server-side sorting turned on:

# ldapsearch -H ldap://10.137.17.132:389 -x -D "uid=3Dadmin,ou=3Dsystem" -w=
 xyz -b "ou=3Dgroups,dc=3Dexample,dc=3Dorg" -s sub  "(&(objectClass=3Dgroup=
OfUniqueNames)(uniqueMember=3Duid=3Doj.c,ou=3DPeople,dc=3Dexample,dc=3Dorg)=
)" cn
# extended LDIF
#
# LDAPv3
# base <ou=3Dgroups,dc=3Dexample,dc=3Dorg> with scope subtree
# filter: (&(objectClass=3DgroupOfUniqueNames)(uniqueMember=3Duid=3Doj.c,ou=
=3DPeople,dc=3Dexample,dc=3Dorg))
# requesting: cn
#

# XYZ BI Manager, XYZ, Groups, example.org
dn: cn=3DXYZ BI Manager,ou=3DXYZ,ou=3DGroups,dc=3Dexample,dc=3Dorg
cn: XYZ BI Manager

# XYZ User, XYZ, Groups, example.org
dn: cn=3DXYZ User,ou=3DXYZ,ou=3DGroups,dc=3Dexample,dc=3Dorg
cn: XYZ User

# XYZ DBManager, XYZ, Groups, example.org
dn: cn=3DXYZ DBManager,ou=3DXYZ,ou=3DGroups,dc=3Dexample,dc=3Dorg
cn: XYZ DBManager

# search result
search: 2
result: 0 Success

# numResponses: 4
# numEntries: 3


> 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, sort-result.ldif
>
>
> Given a partition with several objects with objectClass=3DinetOrgPerson, =
we want to be able to perform a search with a server-side-sort request cont=
rol.=20
> The following ldapsearch query was giving the correct results in ApacheDS=
 2.0.0 M19:
> ldapsearch -H ldap://localhost:10389 -x -D "uid=3Dadmin,ou=3Dsystem" -W -=
b "dc=3Dexample,dc=3Dcom" -s sub -a always -z 1000 "(objectClass=3DinetOrgP=
erson)" "objectClass" -E sss=3D-cn:2.5.13.2
> However in ApacheDS 2.0.0 M20, we get the following error upon running th=
e 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
>   =20
>   SearchRequest
>         baseDn : 'dc=3Dexample,dc=3Dcom'
>         filter : '(objectCla
>  ss=3Dinetorgperson:[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@38b18ca0Sor=
tRequestControlImpl [sortKeys=3D[SortKey : [cn, 2.5.13.2,reverse]]]: java.i=
o.IOException: The system cannot find the path specified


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