[
https://issues.apache.org/jira/browse/DIRSERVER-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862878#comment-16862878
]
Emmanuel Lecharny commented on DIRSERVER-2248:
----------------------------------------------
Ok, the problem is that the {{SchemaManager}} only loads the schemas that are
enabled, then later on, the schema {{LdifPartition}} is loaded but the disabled
schema elements aren't in the {{SchemaManager}} when we load all the schema
elements, leading to those errors being produced.
Sadly, it's not just that we have errors in the logs: if we enable a schema on
a started server, the {{SchemaManager}} is not updated accordingly, and we will
have some missing elements in it.
We must allow the {{SchemaManager}} to load values which can't be normalized
when the {{SchemaManager}} is in {{relaxed}} mode, and we must have the schema
{{LdifPartition}} be loaded using a {{relaxed}} {{Schemamanager}}.
> The server generates some errors when starting (Schema isues)
> -------------------------------------------------------------
>
> Key: DIRSERVER-2248
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2248
> Project: Directory ApacheDS
> Issue Type: New Feature
> Affects Versions: 2.0.0.AM25
> Reporter: Emmanuel Lecharny
> Priority: Major
> Fix For: 2.0.0.AM26
>
>
> When we start the server, we get many erros like :
> {noformat}
> [23:59:05] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
> ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
> handle NameAndOptionalUID normalization with objects of class:
> apacheDnsDomainName
> {noformat}
> The problem is due to some schema elements can't be properly loaded, due to
> some missing dependencies. Typically, we are trying to load this entry :
> {noformat}
> version: 1
> dn: m-oid=1.3.6.1.4.1.18060.0.4.2.2.6,ou=attributeTypes,cn=apachedns,ou=schema
> m-singlevalue: TRUE
> m-obsolete: FALSE
> m-description: The domain name of the name server that was the primary source
> of data for this zone
> m-usage: USER_APPLICATIONS
> creatorsname: uid=admin,ou=system
> m-collective: FALSE
> m-oid: 1.3.6.1.4.1.18060.0.4.2.2.6
> m-supattributetype: apacheDnsDomainName
> m-nousermodification: FALSE
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.26
> objectclass: metaAttributeType
> objectclass: metaTop
> objectclass: top
> m-name: apacheDnsSoaMName
> m-equality: caseIgnoreIA5Match
> {noformat}
> This AttributeType does have a {{SUP}} AttributeType,
> {{apacheDnsDomainName}}, which is not already loaded, as this schema
> ({{ApacheDNS}}) is not enabled, so the Registries does not know about it.
> That leaves the resulting Entry with a missing attribute.
> The consequence is that we can't anymore modify this entry, thus the
> associated LDIF file, properly when the server is running.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
