You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2007/08/17 09:42:30 UTC

[jira] Assigned: (DIRSERVER-911) Syntax length definitions in schemas exported from LDAP Studio throws exception on Apache DS start-up.

     [ https://issues.apache.org/jira/browse/DIRSERVER-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny reassigned DIRSERVER-911:
-------------------------------------------

    Assignee: Emmanuel Lecharny

> Syntax length definitions in schemas exported from LDAP Studio throws exception on Apache DS start-up.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-911
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-911
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: schema
>    Affects Versions: 1.5.0
>         Environment: Mac OS X 10.4.9
>            Reporter: Damien Tougas
>            Assignee: Emmanuel Lecharny
>             Fix For: 1.5.1
>
>
> I opened the following schema into LDAP Studio:
> http://wiki.mozilla.org/MailNews:Mozilla_LDAP_Address_Book_Schema
> I then exported the schema into LDIF format so that I could import it into Apache DS.
> The import into Apache DS runs without errors. When I restart the directory server, it fails to start and the following exception is found in the log file:
> [10:50:47] ERROR [org.apache.directory.daemon.Bootstrapper] - Failed on org.apache.directory.server.Service.init(InstallationLayout, String[])
> javax.naming.NamingException: Unknown syntax OID 1.3.6.1.4.1.1466.115.121.1.26{256}
> 	at org.apache.directory.server.schema.registries.DefaultSyntaxRegistry.lookup(DefaultSyntaxRegistry.java:84)
> 	at org.apache.directory.server.core.schema.AttributeTypeImpl.getSyntax(AttributeTypeImpl.java:197)
> 	at org.apache.directory.server.core.DefaultDirectoryService.initialize(DefaultDirectoryService.java:965)
> 	at org.apache.directory.server.core.DefaultDirectoryService.startup(DefaultDirectoryService.java:254)
> 	at org.apache.directory.server.core.jndi.AbstractContextFactory.getInitialContext(AbstractContextFactory.java:118)
> 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
> 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
> 	at javax.naming.InitialContext.init(InitialContext.java:223)
> 	at javax.naming.InitialContext.<init>(InitialContext.java:197)
> 	at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82)
> 	at org.apache.directory.server.Service.init(Service.java:96)
> 	at org.apache.directory.daemon.Bootstrapper.callInit(Bootstrapper.java:151)
> 	at org.apache.directory.daemon.JsvcBootstrapper.init(JsvcBootstrapper.java:56)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:160)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.