Details

      Description

      I've come across a a directory where they have alot of objects named with #, e.g.
      12345678911#38SA

      Sometimes the LDAP search fails in Studio while it works in other tools.
      If I search for something like this:
      (workforceID=200511230101)
      I should get two DNs back, Studio failes after retrieving the first one named 200511230101,
      the other is named 200511230101#38SA and Studio gives me this error:

      Error while performing search

      • expecting EOF, found '38'
        org.apache.directory.shared.ldap.model.exception.LdapInvalidDnException: expecting EOF, found '38'
        at org.apache.directory.shared.ldap.model.name.ComplexDnParser.parseDn(ComplexDnParser.java:56)
        at org.apache.directory.shared.ldap.model.name.Dn.parseInternal(Dn.java:1321)
        at org.apache.directory.shared.ldap.model.name.Dn.<init>(Dn.java:282)
        at org.apache.directory.shared.ldap.model.name.Dn.<init>(Dn.java:208)
        at org.apache.directory.studio.ldapbrowser.core.utils.JNDIUtils.getDn(JNDIUtils.java:46)
        at org.apache.directory.studio.ldapbrowser.core.jobs.SearchRunnable.searchAndUpdateModel(SearchRunnable.java:329)
        at org.apache.directory.studio.ldapbrowser.core.jobs.SearchRunnable.run(SearchRunnable.java:192)
        at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:109)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
        Caused by: line 1:16: expecting EOF, found '38'
        at antlr.Parser.match(Parser.java:211)
        at org.apache.directory.shared.ldap.model.name.AntlrDnParser.relativeDistinguishedNames(AntlrDnParser.java:338)
        at org.apache.directory.shared.ldap.model.name.ComplexDnParser.parseDn(ComplexDnParser.java:52)
        ... 8 more

      expecting EOF, found '38'

        Issue Links

          Activity

          Hide
          Pierre-Arnaud Marcelot added a comment -

          Thanks for reporting the issue.

          This error is due to a bug in our DN parser. I opened a separate issue about it: DIRAPI-88 (RDN parsing fails with values containing a # character followed by other characters)

          Show
          Pierre-Arnaud Marcelot added a comment - Thanks for reporting the issue. This error is due to a bug in our DN parser. I opened a separate issue about it: DIRAPI-88 (RDN parsing fails with values containing a # character followed by other characters)
          Hide
          Pierre-Arnaud Marcelot added a comment -

          DN parser fixed by Emmanuel at revision 1344275.

          http://svn.apache.org/viewvc?rev=1344275&view=rev

          Show
          Pierre-Arnaud Marcelot added a comment - DN parser fixed by Emmanuel at revision 1344275. http://svn.apache.org/viewvc?rev=1344275&view=rev

            People

            • Assignee:
              Unassigned
              Reporter:
              Aleks M
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development