We have an issue with apacheds-2.0.0-M15 on OS HP-UX. When the server stopped brutally (unix kill command)

never start again.

 

How is the way to stoped the server?

 

Has this bug a work arround?

 

Thanks in advance and Best Regards,

Hernan

 

= = = =  The following is the history about it case = = = =

 

This clearly sounds like a bug. I guess you stopped the server brutally,

and tried to start it again.

My get on this is that the data weren't flushed on disk correctly when

you (probably) killed the server.

 

We are working on a replacement for JDBM, which is the backend we are using.

 

 

 

We have installed apacheds-2.0.0-M15 on OS HP-UX.

 

When we tried stopping and starting the server it fails. The server not starting again, only if we installing again.

 

Enviroment:

OS  HP-UX  B.11.31 U ia64

Java

java version "1.6.0.10"

Java(TM) SE Runtime Environment (build 1.6.0.10-jinteg_11_mar_2011_09_19-b00)

Java HotSpot(TM) Server VM (build 19.1-b02-jinteg:2011mar11-07:33, mixed mode)

 

 

Above the log file messages:

[16:25:25] ERROR [org.apache.directory.server.UberjarMain] - Failed to start the service.

org.apache.directory.api.ldap.model.exception.LdapOtherException: java.lang.Integer cannot be cast to java.lang.Long

        at org.apache.directory.server.core.api.partition.AbstractPartition.initialize(AbstractPartition.java:84)

        at org.apache.directory.server.core.DefaultDirectoryService.initialize(DefaultDirectoryService.java:1820)

        at org.apache.directory.server.core.DefaultDirectoryService.startup(DefaultDirectoryService.java:1248)

        at org.apache.directory.server.ApacheDsService.initDirectoryService(ApacheDsService.java:315)

        at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:179)

        at org.apache.directory.server.UberjarMain.start(UberjarMain.java:76)

        at org.apache.directory.server.UberjarMain.main(UberjarMain.java:54)

Caused by: org.apache.directory.api.ldap.model.exception.LdapOtherException: java.lang.Integer cannot be cast to java.lang.Long

        at org.apache.directory.server.core.api.partition.AbstractPartition.initialize(AbstractPartition.java:84)

        at org.apache.directory.server.core.shared.partition.DefaultPartitionNexus.addContextPartition(DefaultPartitionNexus.java:829)

        at org.apache.directory.server.core.shared.partition.DefaultPartitionNexus.doInit(DefaultPartitionNexus.java:218)

        at org.apache.directory.server.core.api.partition.AbstractPartition.initialize(AbstractPartition.java:79)

        ... 6 more

Caused by: java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Long

        at org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmTable.<init>(JdbmTable.java:166)

        at org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmIndex.initTables(JdbmIndex.java:219)

        at org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmIndex.init(JdbmIndex.java:170)

        at org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmPartition.convertAndInit(JdbmPartition.java:453)

        at org.apache.directory.server.core.partition.impl.btree.AbstractBTreePartition.setupSystemIndices(AbstractBTreePartition.java:353)

        at org.apache.directory.server.core.partition.impl.btree.AbstractBTreePartition.doInit(AbstractBTreePartition.java:519)

        at org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmPartition.doInit(JdbmPartition.java:153)

        at org.apache.directory.server.core.api.partition.AbstractPartition.initialize(AbstractPartition.java:79)

        ... 9 more

 

Thanks in advance and Best Regards,

Hernan

 

Answer

This clearly sounds like a bug. I guess you stopped the server brutally,

and tried to start it again.

My get on this is that the data weren't flushed on disk correctly when

you (probably) killed the server.

 

We are working on a replacement for JDBM, which is the backend we are using.