[
https://issues.apache.org/jira/browse/DIRSERVER-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-381.
---------------------------------------
Closing all issues created in 2005 and before which are marked resolved
> Parser failure on name: Antlr exception trace: line 15:7: unexpected char: '#'
> ------------------------------------------------------------------------------
>
> Key: DIRSERVER-381
> URL: https://issues.apache.org/jira/browse/DIRSERVER-381
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Nick Faiz
> Assigned To: Alex Karasulu
> 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
> org.apache.ldap.common.name.antlrTypeLexer.nextToken(antlrTypeLexer.java:147)
> at antlr.TokenStreamSelector.nextToken(TokenStreamSelector.java:64)
> at antlr.TokenBuffer.fill(TokenBuffer.java:69)
> at antlr.TokenBuffer.LA(TokenBuffer.java:80)
> at antlr.LLkParser.LA(LLkParser.java:52)
> at antlr.Parser.match(Parser.java:212)
> at
> org.apache.ldap.common.name.antlrNameParser.attributeTypeAndValue(antlrNameParser.java:179)
> 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: [EMAIL PROTECTED]
> 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
> (2.5.4.31), 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 server.properties file).
> Cheers,
> Nick
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
