directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <directory-...@incubator.apache.org>
Subject [jira] Updated: (DIREVE-165) Parser failure on name: Antlr exception trace: line 15:7: unexpected char: '#'
Date Fri, 17 Jun 2005 02:49:50 GMT
     [ http://issues.apache.org/jira/browse/DIREVE-165?page=all ]

Alex Karasulu updated DIREVE-165:
---------------------------------

    Summary: Parser failure on name: Antlr exception trace: line 15:7: unexpected char: '#'
 (was: searchFilter for 2 Parser failure on name: Antlr exception trace: line 15:7: unexpected
char: '#')

<biv> hey aok - is it possible to have DIREVE-165 edited to have a more readable title?
Can you get rid of the leading 'searchFilter for 2 '? I dont have the editissue perm.<biv>
hey aok - is it possible to have DIREVE-165 edited to have a more readable title? Can you
get rid of the leading 'searchFilter for 2 '? I dont have the editissue perm.
<aok> ok let me look
<biv> tnx
<aok> ok let me look
<biv> tnx

> Parser failure on name: Antlr exception trace: line 15:7: unexpected char: '#'
> ------------------------------------------------------------------------------
>
>          Key: DIREVE-165
>          URL: http://issues.apache.org/jira/browse/DIREVE-165
>      Project: Directory Server
>         Type: Bug
>     Versions: 0.9.1
>     Reporter: nick faiz
>     Assignee: 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: ldapusera@testingarea.org
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message