[
https://issues.apache.org/jira/browse/DIRSERVER-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1390:
-----------------------------------------
Fix Version/s: (was: 1.5.5)
2.0.0-RC1
Postponed to 2.0.0-RC1
> Attribute caching issues - warning and error messages thrown on startup
> -----------------------------------------------------------------------
>
> Key: DIRSERVER-1390
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1390
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.4
> Environment: Windows XP, Intel Based PC Architecture.
> Reporter: Sumit Goyal
> Fix For: 2.0.0-RC1
>
>
> We define a few custom object classes (in turn having custom attributes). We
> specify their caching in the server.xml file under <indexedAttributes> as
> "<jdbmIndex attributeId="tdsFullyQualifiedObjectId" cacheSize="100"/>".
> (we are specifying pre-defined attributes the similiar way i.e: "<jdbmIndex
> attributeId="dc" cacheSize="100"/>")
> When I start my server, I get messages like:
> [11:58:06] WARN
> [org.apache.directory.server.schema.registries.DefaultOidRegistry] - OID for
> name 'tdsFullyQualifiedObjectId' was not found within the OID
> registry
> whereas, the attribute is there in the schema. And these messages are
> thrown only for custom attributes.
> We replaced attribute name with its OID in the server.xml. Now the warning
> has changed to an error stating:
> [10:02:23] ERROR
> [org.apache.directory.server.schema.registries.DefaultAttribute
> TypeRegistry] - attributeType w/ OID 1.3.6.1.4.1.15265.0.41 not registered!
> From the search performance, it looks like the caching is also not being done
> for these.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
