You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org> on 2007/10/05 15:42:50 UTC
[jira] Created: (DIRSERVER-1083) Search on an custom attribute
added to the dynamic schema fails when no result is found
Search on an custom attribute added to the dynamic schema fails when no result is found
---------------------------------------------------------------------------------------
Key: DIRSERVER-1083
URL: https://issues.apache.org/jira/browse/DIRSERVER-1083
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 1.5.2
Reporter: Pierre-Arnaud Marcelot
Priority: Critical
When searching on a custom attribute added to the dynamic schema, I received an error in Directory Studio:
Error while performing search
[LDAP: error code 80 - failed on search operation: Unexpected exception.]
This error only occurs when no result is found. If one or more results are found, they are correctly displayed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1083) Search on an custom attribute
added to the dynamic schema fails when no result is found
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1083:
-----------------------------------------
Affects Version/s: (was: 1.5.2)
bigbang
Fix Version/s: 1.5.2
Is this is still a problem? If so, it has to be fixed
> Search on an custom attribute added to the dynamic schema fails when no result is found
> ---------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1083
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1083
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: bigbang
> Reporter: Pierre-Arnaud Marcelot
> Priority: Critical
> Fix For: 1.5.2
>
> Attachments: active-directory.ldif
>
>
> When searching on a custom attribute added to the dynamic schema, I received an error in Directory Studio:
> Error while performing search
> [LDAP: error code 80 - failed on search operation: Unexpected exception.]
> This error only occurs when no result is found. If one or more results are found, they are correctly displayed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1083) Search on an custom attribute
added to the dynamic schema fails when no result is found
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578382#action_12578382 ]
Pierre-Arnaud Marcelot commented on DIRSERVER-1083:
---------------------------------------------------
Yeah, the problem is still there.
But the error has changed:
[LDAP: error code 33 - failed on search operation: Unexpected exception.]
> Search on an custom attribute added to the dynamic schema fails when no result is found
> ---------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1083
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1083
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: bigbang
> Reporter: Pierre-Arnaud Marcelot
> Priority: Critical
> Fix For: 1.5.2
>
> Attachments: active-directory.ldif
>
>
> When searching on a custom attribute added to the dynamic schema, I received an error in Directory Studio:
> Error while performing search
> [LDAP: error code 80 - failed on search operation: Unexpected exception.]
> This error only occurs when no result is found. If one or more results are found, they are correctly displayed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-1083) Search on an custom attribute added
to the dynamic schema fails when no result is found
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu closed DIRSERVER-1083.
------------------------------------
Resolution: Invalid
I added a test case here to demonstrate what's going on:
http://svn.apache.org/viewvc?view=rev&revision=643127
LDAP search requires matchingRule to figure out how to conduct candidate matching for various assertions. Without a matchingRule on the attributes used in filter assertions, the server cannot effectively search for your entry based on your search criteria. The server uses comparators and normalizers that are associated matchingRules to normalize and compare values.
Right now the server is defaulting to no op normalizers and comparators when it cannot find a matchingRule for this attribute you want to search. The no-op defaults presumes some binary data. However you're using a human readable syntax. So what's happening is the server is treating your attribute value as binary in some places and bombing out when expecting a string in others.
Right now it's pretty sad that the server let you search on this attribute at all without matchingRules. I don't know if attributeType definitions without MRs are allowed in LDAP. I thought they are but if they don't have a matchingRule they cannot be used in the DN or in filter expressions. I may be wrong.
Please confirm with the RFCs for the exact behavior under these circumstances and I'll make sure we comply. Thanks!
> Search on an custom attribute added to the dynamic schema fails when no result is found
> ---------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1083
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1083
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: bigbang
> Reporter: Pierre-Arnaud Marcelot
> Assignee: Alex Karasulu
> Priority: Critical
> Fix For: 1.5.2
>
> Attachments: active-directory.ldif
>
>
> When searching on a custom attribute added to the dynamic schema, I received an error in Directory Studio:
> Error while performing search
> [LDAP: error code 80 - failed on search operation: Unexpected exception.]
> This error only occurs when no result is found. If one or more results are found, they are correctly displayed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRSERVER-1083) Search on an custom attribute
added to the dynamic schema fails when no result is found
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu reassigned DIRSERVER-1083:
----------------------------------------
Assignee: Alex Karasulu
> Search on an custom attribute added to the dynamic schema fails when no result is found
> ---------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1083
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1083
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: bigbang
> Reporter: Pierre-Arnaud Marcelot
> Assignee: Alex Karasulu
> Priority: Critical
> Fix For: 1.5.2
>
> Attachments: active-directory.ldif
>
>
> When searching on a custom attribute added to the dynamic schema, I received an error in Directory Studio:
> Error while performing search
> [LDAP: error code 80 - failed on search operation: Unexpected exception.]
> This error only occurs when no result is found. If one or more results are found, they are correctly displayed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1083) Search on an custom attribute
added to the dynamic schema fails when no result is found
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre-Arnaud Marcelot updated DIRSERVER-1083:
----------------------------------------------
Attachment: active-directory.ldif
This is the ldif i'm using to test this issue.
When searching with filter: (pwdLastSet=toto), I get the right entry
When searching with filter: (pwdLastSet=fsdfs), I get an error.
> Search on an custom attribute added to the dynamic schema fails when no result is found
> ---------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1083
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1083
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Pierre-Arnaud Marcelot
> Priority: Critical
> Attachments: active-directory.ldif
>
>
> When searching on a custom attribute added to the dynamic schema, I received an error in Directory Studio:
> Error while performing search
> [LDAP: error code 80 - failed on search operation: Unexpected exception.]
> This error only occurs when no result is found. If one or more results are found, they are correctly displayed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1083) Search on an custom attribute
added to the dynamic schema fails when no result is found
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583821#action_12583821 ]
Alex Karasulu commented on DIRSERVER-1083:
------------------------------------------
Looks like there are no matchingRules specified for the attribute and the server is freaking out. I have a test here setup to load your LDIF. I will add some matching rules for it on this pwdLastSet attribute to see if that resolves the problem.
> Search on an custom attribute added to the dynamic schema fails when no result is found
> ---------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1083
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1083
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: bigbang
> Reporter: Pierre-Arnaud Marcelot
> Assignee: Alex Karasulu
> Priority: Critical
> Fix For: 1.5.2
>
> Attachments: active-directory.ldif
>
>
> When searching on a custom attribute added to the dynamic schema, I received an error in Directory Studio:
> Error while performing search
> [LDAP: error code 80 - failed on search operation: Unexpected exception.]
> This error only occurs when no result is found. If one or more results are found, they are correctly displayed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.