directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Ayyagari (JIRA)" <>
Subject [jira] [Closed] (DIRSERVER-1390) Attribute caching issues - warning and error messages thrown on startup
Date Thu, 02 Jun 2011 10:47:47 GMT


Kiran Ayyagari closed DIRSERVER-1390.

    Resolution: Fixed

These warnings were fixed long time ago.

> Attribute caching issues - warning and error messages thrown on startup
> -----------------------------------------------------------------------
>                 Key: DIRSERVER-1390
>                 URL:
>             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-M1
> 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"
> When I start my server, I get messages like:
> [11:58:06] WARN  [] -
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  [  TypeRegistry]
- attributeType w/ OID 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.
For more information on JIRA, see:

View raw message