Markus, Emmanuel note that the 1.0.0 server.xml file will not work with 1.0.1 and 1.0.2 since we changed the OID bases used by Apache. We were using the incorrect OID branch numbers: this was my fault. We realized this after the 1.0.0 release and corrected it in the 1.0.1 release.
This base 1.2.6.1.4.1.18060.... is incorrect in 1.0.0 and is now 1.3.6.1.4.1.18060... Sorry about this. If you use the server.xml file in the 1.0.x branch that Emmanuel mentioned in the server-main project that should work. Regards, Alex On 3/28/07, Markus Pohle <[EMAIL PROTECTED]> wrote:
Hi there, as building the apacheds-1.0.2 snapshot was successful i tried to start it up. what i did is that i only used the java .jar files and fired up the server with a self written shell script. as server configuration file i used my 1.0.0 server.xml file. shell script is here: http://www.douglas-informatik.de/apacheds/startApacheDs.sh server.xml is here: http://www.douglas-informatik.de/apacheds/server.xml.orig what happened when i fired up the apacheds is the following: [14:04:37] WARN [ org.apache.directory.server.core.schema.AttributeTypeRegistryMonitorAdapter ] - Failed to look up the attribute type registry:1.2.6.1.4.1. 18060.1.1.1.3.1 javax.naming.NamingException: attributeType w/ OID 1.2.6.1.4.1.18060.1.1.1.3.1 not registered! at org.apache.directory.server.core.schema.GlobalAttributeTypeRegistry.lookup (GlobalAttributeTypeRegistry.java:153) at org.apache.directory.server.core.partition.impl.btree.BTreePartition.init( BTreePartition.java:181) at org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmPartition.init (JdbmPartition.java:189) at org.apache.directory.server.core.partition.DefaultPartitionNexus.initializeSystemPartition (DefaultPartitionNexus.java:363) at org.apache.directory.server.core.partition.DefaultPartitionNexus.init( DefaultPartitionNexus.java:200) at org.apache.directory.server.core.DefaultDirectoryService.initialize( DefaultDirectoryService.java:837) at org.apache.directory.server.core.DefaultDirectoryService.startup( DefaultDirectoryService.java:230) at org.apache.directory.server.core.jndi.AbstractContextFactory.getInitialContext (AbstractContextFactory.java:118) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:679) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:259) at javax.naming.InitialContext.init(InitialContext.java:235) at javax.naming.InitialContext.<init>(InitialContext.java:209) at org.apache.directory.server.Service.init(Service.java:96) at org.apache.directory.server.UberjarMain.main(UberjarMain.java :54) any idea why this happened? what i tried then is to modify the server.xml config file that was build thru maven install process of 1.0.2 version. the modified server.xml file can be found here: http://www.douglas-informatik.de/apacheds/server.xml.modified i then fired up the server what was successful and then connected against the server with JXplorer ldap tool. i then tried to import a ldif file, which i could process successfully with the 1.0.0 version and the following error occured: An error occured while processing the LDIF file: javax.naming.NameAlreadyBoundException: [LDAP: error code 68 - failed to add entry dc=VERWALTUNG,dc=douglasholding: 0.9.2342.19200300.100.1.25=verwaltung, 0.9.2342.19200300.100.1.25=douglasholding already exists!]; remaining name 'dc=VERWALTUNG,dc=douglasholding anybody an idea why this happened? thx Markus -- WEBUNITY - Internet, Consulting, Neue Medien Markus Pohle (SCJP) GPG Public Key Block available at: http://www.webunity.de/[EMAIL PROTECTED]
