Uploaded image for project: 'Directory ApacheDS'
  1. Directory ApacheDS
  2. DIRSERVER-2341

Apache DS stops serving requests after error

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.0.AM26
    • Fix Version/s: 2.0.0.AM26
    • Component/s: jdbm
    • Labels:
    • Environment:
      Apache DS 2.0.0 AM 26 running over RHEL 7.8 and Oracle JDK 1.8.0_241-b07.
    • Flags:
      Important

      Description

      Hi everybody,

      today we had another issues with Apache DS on a production environment.

      In the morning, while the system was being loaded (every morning we load new users into the system) we had the following error in the logs:

       

      @

       

      [05:04:41] WARN [org.apache.directory.server.ldap.LdapProtocolHandler] - Unexpected exception forcing session to close: sending disconnect notice to client.
      java.lang.Error: ERR_554 double get for block 159java.lang.Error: ERR_554 double get for block 159 at jdbm.recman.RecordFile.get(RecordFile.java:185) at jdbm.recman.PhysicalRowIdManager.fetch(PhysicalRowIdManager.java:128) at jdbm.recman.BaseRecordManager.fetch(BaseRecordManager.java:323) at jdbm.btree.BPage.loadBPage(BPage.java:949) at jdbm.btree.BPage.childBPage(BPage.java:938) at jdbm.btree.BPage.insert(BPage.java:380) at jdbm.btree.BPage.insert(BPage.java:381) at jdbm.btree.BPage.insert(BPage.java:381) at jdbm.btree.BTree.insert(BTree.java:302) at org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmTable.put(JdbmTable.java:541) at org.apache.directory.server.ldap.replication.provider.ReplicaEventLog.log(ReplicaEventLog.java:176) at org.apache.directory.server.ldap.replication.provider.SyncReplSearchListener.entryAdded(SyncReplSearchListener.java:224) at org.apache.directory.server.core.event.EventInterceptor.fire(EventInterceptor.java:131) at org.apache.directory.server.core.event.EventInterceptor.add(EventInterceptor.java:267) at org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:341) at org.apache.directory.server.core.subtree.SubentryInterceptor.add(SubentryInterceptor.java:1034) at org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:341) at org.apache.directory.server.core.collective.CollectiveAttributeInterceptor.add(CollectiveAttributeInterceptor.java:138) at org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:341) at org.apache.directory.server.core.operational.OperationalAttributeInterceptor.add(OperationalAttributeInterceptor.java:327) at org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:341) at org.apache.directory.server.core.schema.SchemaInterceptor.add(SchemaInterceptor.java:1132) at org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:341) at org.apache.directory.server.core.hash.ConfigurableHashingInterceptor.add(ConfigurableHashingInterceptor.java:91) at org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:341) at org.apache.directory.server.core.exception.ExceptionInterceptor.add(ExceptionInterceptor.java:185) at org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:341)
       
      

       

       

      The problem is that after this error Apache DS stopped serving requests, the only solution we had was to stop the server and restart it.

       

      Is there any available fix or workaround for this issue?

       

      Please help, thanks in advance and best regards,

      Andrea

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              acampana74 Andrea Campana
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: