directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Petr Špaček (JIRA) <j...@apache.org>
Subject [jira] [Created] (DIRSTUDIO-871) Error during on-line schema loading: expecting '\n', found '<EOF>'
Date Thu, 07 Feb 2013 12:51:12 GMT
Petr Špaček created DIRSTUDIO-871:
-------------------------------------

             Summary: Error during on-line schema loading: expecting '\n', found '<EOF>'
                 Key: DIRSTUDIO-871
                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-871
             Project: Directory Studio
          Issue Type: Bug
          Components: studio-schemaeditor
    Affects Versions: 2.0.0-M4
            Reporter: Petr Špaček
            Priority: Minor


Hello,

I'm not 100 % sure if the error is caused by bug in schema parser or if the schema itself
is buggy.

During on-line schema loading following error is thown to the console:

Error reading schema: attributeTypes = ( 2.16.840.1.113730.3.1.2110 NAME 'unhashed#user#password'
DESC 'internal server defined attribute type' SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 NO-USER-MODIFICATION
USAGE directoryOperation X-ORIGIN '389-Directory/1.2.11.16' )
ERR_04229 Parser failure on attribute type description:
	( 2.16.840.1.113730.3.1.2110 NAME 'unhashed#user#password' DESC 'internal server defined
attribute type' SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 NO-USER-MODIFICATION USAGE directoryOperation
X-ORIGIN '389-Directory/1.2.11.16' )
Antlr message: expecting '\n', found '<EOF>'
org.apache.directory.api.ldap.model.exception.LdapInvalidAttributeValueException: ERR_10006
Comparator OID nsUserRDNComponent-oid is not a valid OID 
	at org.apache.directory.api.ldap.schemaloader.SchemaEntityFactory.getOid(SchemaEntityFactory.java:122)
	at org.apache.directory.api.ldap.schemaloader.SchemaEntityFactory.getAttributeType(SchemaEntityFactory.java:873)
	at org.apache.directory.api.ldap.schemamanager.impl.DefaultSchemaManager.addAttributeTypes(DefaultSchemaManager.java:794)
	at org.apache.directory.api.ldap.schemamanager.impl.DefaultSchemaManager.addSchemaObjects(DefaultSchemaManager.java:258)
	at org.apache.directory.api.ldap.schemamanager.impl.DefaultSchemaManager.load(DefaultSchemaManager.java:747)
	at org.apache.directory.api.ldap.schemamanager.impl.DefaultSchemaManager.loadDepsFirst(DefaultSchemaManager.java:1172)
	at org.apache.directory.api.ldap.schemamanager.impl.DefaultSchemaManager.loadWithDeps(DefaultSchemaManager.java:1097)
	at org.apache.directory.api.ldap.schemamanager.impl.DefaultSchemaManager.loadAllEnabled(DefaultSchemaManager.java:987)
	at org.apache.directory.studio.schemaeditor.model.schemachecker.SchemaChecker$3.run(SchemaChecker.java:274)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

I will add complete schema to the ticket if I find the right button :-)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message