directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Goyal (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-1390) Attribute caching issues - warning and error messages thrown on startup
Date Thu, 30 Jul 2009 05:18:14 GMT


Sumit Goyal commented on DIRSERVER-1390:

Schema definition is:

dn: m-oid=,ou=attributeTypes,cn=schema,ou=schema
changetype: add
objectClass: metaAttributeType
objectClass: metaTop
objectClass: top
m-name: tdsFullyQualifiedObjectId
m-singlevalue: TRUE
m-equality: caseIgnoreMatch
m-substr: caseIgnoreSubstringsMatch

Please elaborate what do you mean when you say if schema is enabled. If that means whether
the schema is added in the server.xml as:
"<jdbmIndex attributeId="tdsFullyQualifiedObjectId" cacheSize="100"/>"
then yes. 

> Attribute caching issues - warning and error messages thrown on startup
> -----------------------------------------------------------------------
>                 Key: DIRSERVER-1390
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.5
>         Environment: Windows XP, Intel Based PC Architecture.
>            Reporter: Sumit Goyal
> 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.
You can reply to this email to add a comment to the issue online.

View raw message