directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Resolved: (DIREVE-165) Parser failure on name: Antlr exception trace: line 15:7: unexpected char: '#'
Date Wed, 24 Aug 2005 17:49:34 GMT
     [ ]
Alex Karasulu resolved DIREVE-165:

    Fix Version: 0.9.2
     Resolution: Invalid

This is not a bug.  You are incorrectly using the member attribute.  According to 2256 this
is the following definition for a member attribute:

attributetype ( NAME 'member'
        DESC 'RFC2256: member of a group'
        SUP distinguishedName )

Notice that member values must be distinguished names.  So your LDIF is invalid since the
member values are not correctt distinguished names.  The server basically chokes trying to
read a DN for groupB in this incorrect filter of (member=groupB).  If you used the proper
values in the LDAP for the member attribute the following filter would work:


Once I fixed the LDIF and ran this search filter it all worked like a champion.

> Parser failure on name: Antlr exception trace: line 15:7: unexpected char: '#'
> ------------------------------------------------------------------------------
>          Key: DIREVE-165
>          URL:
>      Project: Directory Server
>         Type: Bug
>     Versions: 0.9.1
>     Reporter: Nick Faiz
>     Assignee: Alex Karasulu
>      Fix For: 0.9.2
>  Attachments: test-userbase.ldif
> This probably only occurs under a certain config. (see below), so it is possible that
the configuration itself is erroneous.
> When running a search on a user, represented in LDIF, below, I hit the following stack
trace with the following search filter:
> search filter:  (member=groupB)
> Parser failure on name:
> 	groupB
> Antlr exception trace:
> line 15:7: unexpected char: '#'
> 	at
> 	at antlr.TokenStreamSelector.nextToken(
> 	at antlr.TokenBuffer.fill(
> 	at antlr.TokenBuffer.LA(
> 	at antlr.LLkParser.LA(
> 	at antlr.Parser.match(
> 	at
> dn: uid=ldapusera,ou=users,ou=system
> cn: ldapusera
> sn: Surname1
> givenname: ldapusera
> objectclass: top
> objectclass: person
> objectclass: organizationalPerson
> objectclass: inetOrgPerson
> ou: Human Resources
> ou: People
> l: Atlassian test subject
> uid: ldapusera
> mail:
> userpassword: passa
> title: groupA
> title: groupB
> member: groupA
> The search filter successfully works on title, uid,  and mail. Perhaps I'm making a mistake
by trying to incorporate the member attribute, from RFC 2256 (, into an inetorgperson
entity? All the same, the error message is mysterious ...
> This problem is occurring on 0.9.1 main, before the addition  of the Spring config. layer
(i.e., Im still setting up with a file).
> Cheers,
> Nick

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message