[
https://issues.apache.org/jira/browse/DIRSERVER-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495396
]
Stefan Zoerner commented on DIRSERVER-927:
------------------------------------------
I was wrong: locality is not an attribute type, but an object class. There is a
severe error in the schema subsystem, if an objectClass name is used in the
attributes list of a search operation.
$ ldapsearch -h magritte -p 10389 -D "uid=admin,ou=system" -w secret -s sub -b
"dc=example,dc=com" "(objectClass=*)" top
ldap_search: Unknown error
ldap_search: additional info: failed on search operation: attributeType w/ OID
2.5.6.0 not registered!
$
It seems, that the search for the attribute types uses a wrong filter.
Do you know, which attributes are requested, when you get "failed on search
operation: attributeType w/ OID 2.5.6.3 not registered!". Does your client
request "locality"?. Or is it still attributes : 'mozillaUseHtmlMail',
'objectClass' ?
> Requesting unknown attribute in search causes query failure
> -----------------------------------------------------------
>
> Key: DIRSERVER-927
> URL: https://issues.apache.org/jira/browse/DIRSERVER-927
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap
> Affects Versions: 1.5.0
> Reporter: Chris Custine
>
> A search request that lists an unknown attribute to be returned causes the
> search request to fail. This is observed in Thunderbird mail client when
> Thunderbird requests the mozilla schema attributes and gets this in response:
> Error while performing search
> [LDAP: error code 54 - failed on search operation: attributeType w/ OID
> 1.3.6.1.4.1.13769.2.1.2 not registered!:
> SearchRequest
> baseDn : 'dc=organicelement,dc=com'
> filter : '(2.5.4.0=*)[14] '
> scope : whole subtree
> typesOnly : false
> 1000
> Time Limit : no limit
> Deref Aliases : deref Always
> attributes : 'mozillaUseHtmlMail', 'objectClass'
> :
> javax.naming.NamingException: attributeType w/ OID 1.3.6.1.4.1.13769.2.1.2
> not registered!
> at
> org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:156)
> at
> org.apache.directory.server.core.partition.impl.btree.BTreeSearchResultEnumeration.next(BTreeSearchResultEnumeration.java:207)
> at
> org.apache.directory.server.core.enumeration.SearchResultFilteringEnumeration.prefetch(SearchResultFilteringEnumeration.java:291)
> at
> org.apache.directory.server.core.enumeration.SearchResultFilteringEnumeration.<init>(SearchResultFilteringEnumeration.java:109)
> at
> org.apache.directory.server.core.collective.CollectiveAttributeService.search(CollectiveAttributeService.java:321)
> at
> org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1234)
> at
> org.apache.directory.server.core.subtree.SubentryService.search(SubentryService.java:245)
> at
> org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1234)
> at
> org.apache.directory.server.core.schema.SchemaService.search(SchemaService.java:464)
> at
> org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1234)
> at
> org.apache.directory.server.core.operational.OperationalAttributeService.search(OperationalAttributeService.java:337)
> at
> org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1234)
> .. clipped
> ]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
