Uploaded image for project: 'Directory Client API'
  1. Directory Client API
  2. DIRAPI-196

Always throw error ERR_04486_VALUE_ALREADY_EXISTS from org.apache.directory.api.ldap.model.entry.DefaultAttribute against AD's attribute dSCorePropagationData when do search operation.

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.0-M22
    • Fix Version/s: 1.0.0-M30
    • Labels:
      None

      Description

      When do search on ADAM, if the entry include attribute "dSCorePropagationData", org.apache.directory.api.ldap.model.entry.DefaultAttribute always throw error "ERR_04486_VALUE_ALREADY_EXISTS ".
      "dSCorePropagationData" is one system attribute, it has mutiple values, when the entry was rdn or moved, one value will be created by system.

        Activity

        Hide
        elecharny Emmanuel Lecharny added a comment -

        Not sure I understand your problem. Can you describe the exact steps you were using to get this error ?

        I find it doutbful you get such an error doing a simple search.

        Show
        elecharny Emmanuel Lecharny added a comment - Not sure I understand your problem. Can you describe the exact steps you were using to get this error ? I find it doutbful you get such an error doing a simple search.
        Hide
        elecharny Emmanuel Lecharny added a comment -

        We really need the code that produces this error.

        Show
        elecharny Emmanuel Lecharny added a comment - We really need the code that produces this error.
        Hide
        elecharny Emmanuel Lecharny added a comment -

        Not enough description, and the part we have is clearly not making any sense. There is no way one can get the mentioned error doing a Search.

        Show
        elecharny Emmanuel Lecharny added a comment - Not enough description, and the part we have is clearly not making any sense. There is no way one can get the mentioned error doing a Search.
        Hide
        elecharny Emmanuel Lecharny added a comment -

        Reopened, the pb is due to some Error log message when the entry contains duplicate attribute while doing a search. The log message should be a warning instead.

        Show
        elecharny Emmanuel Lecharny added a comment - Reopened, the pb is due to some Error log message when the entry contains duplicate attribute while doing a search. The log message should be a warning instead.
        Hide
        SuperFly Matt Willson added a comment -

        Errors may flood the log if for some reason the LDAP server contains attributes that have multiple duplicate values. When this occurs there will never be any adverse effects in the LDAP API code because it won't ever contain the dupe values. Thus the log should be a warning.

        This is easily duplicated in the SearchResultEntryTest Unit Test. If you change the ByteBuffer stream to include duplicate values for one attribute.

        Show
        SuperFly Matt Willson added a comment - Errors may flood the log if for some reason the LDAP server contains attributes that have multiple duplicate values. When this occurs there will never be any adverse effects in the LDAP API code because it won't ever contain the dupe values. Thus the log should be a warning. This is easily duplicated in the SearchResultEntryTest Unit Test. If you change the ByteBuffer stream to include duplicate values for one attribute.
        Hide
        elecharny Emmanuel Lecharny added a comment -
        Show
        elecharny Emmanuel Lecharny added a comment - Solved with http://svn.apache.org/r1670438

          People

          • Assignee:
            Unassigned
            Reporter:
            hxbon1y Robert Hou
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development