[jira] [Commented] (DIRSERVER-1857) Allow registration of an LdapsInitializer at the LdapServer
[ https://issues.apache.org/jira/browse/DIRSERVER-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861066#comment-16861066 ] Rashid Mahmood commented on DIRSERVER-1857: --- We are facing similar problem where we want to setup LdapServer with Mutual SSL Authentication. The issue was reported in 2013 and till yet not fixed. we are using 2.0.0.AM25 version. > Allow registration of an LdapsInitializer at the LdapServer > --- > > Key: DIRSERVER-1857 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1857 > Project: Directory ApacheDS > Issue Type: Improvement >Affects Versions: 2.0.0-M12 >Reporter: Achim Willems >Priority: Major > > Due to a BSI directive we need mutual authentication for SSL/TLS connections. > BSI (Bundesamt für Sicherheit in der Informationstechnik) is a german > governmental organization. This means, that we cannot ignore this directive. > The current implementation of org.apache.directory.server.ldap.LdapServer > uses the static method > org.apache.directory.server.ldap.handlers.ssl.LdapsInitializer.init to > initialize the SSL communication. > It would be helpful to have an LdapsInitializer interface with a default > implementation (i.e. the current implementation is the default) and the > possibility to register this interface at the LdapServer. > We then could implement our own version of the initializer to establish the > necessary behaviour. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035118#comment-17035118 ] Rashid Mahmood commented on DIRSERVER-2299: --- I already mentioned in issue description which version we are using. If new version is using one .db file then why repair command generates a zero byte size no named .db file, see 4th comment. I still dont understand why index information was lost after server stop, possible reason could be that indexes were never written on file-system and were kept in memory. Is there any tool from ApacheDS to validate the database for corruption and to explore the meta information inside database? We are afraid that in production environment we can face severe search issues (because of indexing) or possible data corruption issues with data replication. Is ApacheDS Production Ready? > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: ApacheDS 2.0.0.AM24-example-structure.png, ApacheDS > 2.0.0.AM25-example-structure.png, after-repair.png, > image-2020-02-06-16-53-48-839.png, image-2020-02-11-17-02-41-811.png, > index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035354#comment-17035354 ] Rashid Mahmood commented on DIRSERVER-2299: --- Thanks for your feeback. Is there planned date for next release? can we expect working Mavibot backend in next release? > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: ApacheDS 2.0.0.AM24-example-structure.png, ApacheDS > 2.0.0.AM25-example-structure.png, after-repair.png, > image-2020-02-06-16-53-48-839.png, image-2020-02-11-17-02-41-811.png, > index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031601#comment-17031601 ] Rashid Mahmood commented on DIRSERVER-2299: --- Update: First time Repair worked and now after every restart Repair is also not working, most of mail/telID attribute entries are not indexed and not searchable. > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashid Mahmood updated DIRSERVER-2299: -- Attachment: image-2020-02-06-16-53-48-839.png > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: image-2020-02-06-16-53-48-839.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031698#comment-17031698 ] Rashid Mahmood commented on DIRSERVER-2299: --- !image-2020-02-06-16-53-48-839.png! After Repair command i see two new DB files were created inside Partitions directory. Where can i configure the Index DB file name and path? As i understood from ApacheDS docs, master data is located inside master.db and each index attribute has its own db file i.e. index-attribute-id.db, Is this true? or everything(master table und index tables) is part of the partition db file, in our case tsi.db for example? > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: image-2020-02-06-16-53-48-839.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashid Mahmood updated DIRSERVER-2299: -- Attachment: index-config.png > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: after-repair.png, image-2020-02-06-16-53-48-839.png, > index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashid Mahmood updated DIRSERVER-2299: -- Attachment: after-repair.png > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: after-repair.png, image-2020-02-06-16-53-48-839.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17032239#comment-17032239 ] Rashid Mahmood commented on DIRSERVER-2299: --- !after-repair.png! !index-config.png! Thanks [~elecharny] Based on the server configuration means under following path \ou=config\ads-directoryserviceid=default\ou=partitions\ads-partitionid=tsi\ou=indexes ? In my file system i can see those two index config files ads-indexattributeid=mail.ldif and ads-indexattributeid=telematikid.ldif but i never saw any automatically generated files in partitions directory. Is some special setting missing? These two attributes and respective indexes are part of our custom schema which was imported during installation. After installation we didnt saw any import error and two index config files were generated under above mentioned path. DB via DN lookup works, can we still conclude DB is corrupted? > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: after-repair.png, image-2020-02-06-16-53-48-839.png, > index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17032293#comment-17032293 ] Rashid Mahmood commented on DIRSERVER-2299: --- Ok, please also verify that for every index an index-name.db file is really created, in our case (either from first start after installation or repair command executions) we dont see any other db files except [partition-name].db. > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: after-repair.png, image-2020-02-06-16-53-48-839.png, > index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSERVER-2299) Missing Indexes after Restart
Rashid Mahmood created DIRSERVER-2299: - Summary: Missing Indexes after Restart Key: DIRSERVER-2299 URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 Project: Directory ApacheDS Issue Type: Bug Components: index, ldap Affects Versions: 2.0.0.AM25 Reporter: Rashid Mahmood We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in our product. Ldap Server and Directory Service are being used in Embedded Mode. During our Tests we found that after Restart, some of the Entries via Indexed Attribute Search Filter are not comming in search result. After considering various possibilities we found that it is Indexing problem. We used Repair commnd and then we see those entries in search results. Why some of the indexes were missing even it was a gracefull shutdown? We want to avoid repair command after every restart unless it is really necessary. Our product will serve in future more than 50K users, we have fear that it would cost us a lot if we encounter those unexpected problems. These are two attributes used in our search filters dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part itions,ads-directoryServiceId=default,ou=config ads-indexattributeid: mail ads-indexHasReverse: FALSE ads-indexcachesize: 1000 objectclass: ads-index objectclass: ads-jdbmIndex objectclass: ads-base objectclass: top ads-enabled: TRUE dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part itions,ads-directoryServiceId=default,ou=config ads-indexattributeid: telID ads-indexHasReverse: FALSE ads-indexcachesize: 1000 objectclass: ads-index objectclass: ads-jdbmIndex objectclass: ads-base objectclass: top ads-enabled: TRUE -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034335#comment-17034335 ] Rashid Mahmood commented on DIRSERVER-2299: --- Any Update on following? * verify that for every index, an index-name.db file is created * repair works as it is supposed to work * why on stop indexes are lost > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: after-repair.png, image-2020-02-06-16-53-48-839.png, > index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17033442#comment-17033442 ] Rashid Mahmood commented on DIRSERVER-2299: --- One more Question: is Mavibot implementation in ApacheDS production ready in version 2.0.0.AM25? > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: after-repair.png, image-2020-02-06-16-53-48-839.png, > index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034449#comment-17034449 ] Rashid Mahmood commented on DIRSERVER-2299: --- I have tested now with 9th Feb Snapshot from [https://repository.apache.org/content/groups/snapshots/org/apache/directory/server/apacheds-service/2.0.0.AM26-SNAPSHOT/] I see no difference in behaviour. > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: after-repair.png, image-2020-02-06-16-53-48-839.png, > index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashid Mahmood updated DIRSERVER-2299: -- Attachment: image-2020-02-11-17-02-41-811.png > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: after-repair.png, image-2020-02-06-16-53-48-839.png, > image-2020-02-11-17-02-41-811.png, index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashid Mahmood updated DIRSERVER-2299: -- Attachment: ApacheDS 2.0.0.AM24-example-structure.png > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: ApacheDS 2.0.0.AM24-example-structure.png, ApacheDS > 2.0.0.AM25-example-structure.png, after-repair.png, > image-2020-02-06-16-53-48-839.png, image-2020-02-11-17-02-41-811.png, > index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashid Mahmood updated DIRSERVER-2299: -- Attachment: ApacheDS 2.0.0.AM25-example-structure.png > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: ApacheDS 2.0.0.AM25-example-structure.png, > after-repair.png, image-2020-02-06-16-53-48-839.png, > image-2020-02-11-17-02-41-811.png, index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Comment Edited] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034568#comment-17034568 ] Rashid Mahmood edited comment on DIRSERVER-2299 at 2/11/20 4:19 PM: I think version AM25 introduced some bug in index handling, see this is the example partition structure in AM25 !ApacheDS 2.0.0.AM25-example-structure.png! this is the example partition structure in M24 which seems to be the same layout what you have written in first comment !ApacheDS 2.0.0.AM24-example-structure.png! was (Author: ramahmoo): I think version AM25 created some bug in index handling, see this is the example partition structure in AM25 !ApacheDS 2.0.0.AM25-example-structure.png! this is the example partition structure in AM24 which seems to be the same layout what you have written in first comment !ApacheDS 2.0.0.AM24-example-structure.png! > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: ApacheDS 2.0.0.AM24-example-structure.png, ApacheDS > 2.0.0.AM25-example-structure.png, after-repair.png, > image-2020-02-06-16-53-48-839.png, image-2020-02-11-17-02-41-811.png, > index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034568#comment-17034568 ] Rashid Mahmood commented on DIRSERVER-2299: --- I think version AM25 created some bug in index handling, see this is the example partition structure in AM25 !ApacheDS 2.0.0.AM25-example-structure.png! this is the example partition structure in AM24 which seems to be the same layout what you have written in first comment !ApacheDS 2.0.0.AM24-example-structure.png! > Missing Indexes after Restart > - > > Key: DIRSERVER-2299 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2299 > Project: Directory ApacheDS > Issue Type: Bug > Components: index, ldap >Affects Versions: 2.0.0.AM25 >Reporter: Rashid Mahmood >Priority: Major > Attachments: ApacheDS 2.0.0.AM24-example-structure.png, ApacheDS > 2.0.0.AM25-example-structure.png, after-repair.png, > image-2020-02-06-16-53-48-839.png, image-2020-02-11-17-02-41-811.png, > index-config.png > > > We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in > our product. Ldap Server and Directory Service are being used in Embedded > Mode. > > During our Tests we found that after Restart, some of the Entries via Indexed > Attribute Search Filter are not comming in search result. After considering > various possibilities we found that it is Indexing problem. We used Repair > commnd and then we see those entries in search results. > > Why some of the indexes were missing even it was a gracefull shutdown? > > We want to avoid repair command after every restart unless it is really > necessary. Our product will serve in future more than 50K users, we have fear > that it would cost us a lot if we encounter those unexpected problems. > > These are two attributes used in our search filters > dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: mail > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part > itions,ads-directoryServiceId=default,ou=config > ads-indexattributeid: telID > ads-indexHasReverse: FALSE > ads-indexcachesize: 1000 > objectclass: ads-index > objectclass: ads-jdbmIndex > objectclass: ads-base > objectclass: top > ads-enabled: TRUE > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2306) Removing pwdAccountLockedTime Attribute with Technical User
[
https://issues.apache.org/jira/browse/DIRSERVER-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089476#comment-17089476
]
Rashid Mahmood commented on DIRSERVER-2306:
---
Delete userPassword attribute and add it once again. This seems to unlock the
user.
1). But what about pwdAccountLockedTime attribute, will this operational
attribute remain setted? if yes which possible problems could occur?
2). Password History remains there or it would be lost?
> Removing pwdAccountLockedTime Attribute with Technical User
> ---
>
> Key: DIRSERVER-2306
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2306
> Project: Directory ApacheDS
> Issue Type: Task
>Affects Versions: 2.0.0-M24
>Reporter: Rashid Mahmood
>Priority: Major
>
> We are connecting to ApacheDS ldap with a technical user created with ACL
> mentioned below. We are able to cover all of requirements except the
> possibility for user to unlock his account, when he tried to unlock the
> account, behind the scene techincal user is unable to remove
> pwdAccountLockedTime attribute and we receive Access Rights error.
> We tried to switch Admin user but then it is contradicting with another
> requirement of pwdHistory and user was able to reuse existing password during
> password change https://issues.apache.org/jira/browse/DIRSERVER-2084
> Is it possible to handle both requirements with one technical user? our
> preference was to handle it with our own user instead of default admin
> {code:java}
> dn: cn=fdLdapAuthorizationRequirementsACISubentry,dc=abc,dc=xyz
> changetype: add
> objectclass: top
> objectclass: subentry
> objectclass: accessControlSubentry
> cn: fdLdapAuthorizationRequirementsACISubentry
> subtreeSpecification: {}
> prescriptiveACI: {
> identificationTag "directoryManagerFullAccessACI",
> precedence 11,
> authenticationLevel simple,
> itemOrUserFirst userFirst:
> {
> userClasses
> {
>name { "uid=fdactmgr,ou=users,ou=system" }
> },
> userPermissions
> {
> {
> protectedItems
> {
> entry, allUserAttributeTypesAndValues
> },
> grantsAndDenials
> {
> grantAdd, grantDiscloseOnError, grantRead,
> grantRemove, grantBrowse, grantExport, grantImport,
> grantModify, grantRename, grantReturnDN,
> grantCompare, grantFilterMatch, grantInvoke
> }
> }
> }
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSERVER-2306) Removing pwdAccountLockedTime Attribute with Technical User
Rashid Mahmood created DIRSERVER-2306:
-
Summary: Removing pwdAccountLockedTime Attribute with Technical
User
Key: DIRSERVER-2306
URL: https://issues.apache.org/jira/browse/DIRSERVER-2306
Project: Directory ApacheDS
Issue Type: Task
Affects Versions: 2.0.0-M24
Reporter: Rashid Mahmood
We are connecting to ApacheDS ldap with a technical user created with ACL
mentioned below. We are able to cover all of requirements except the
possibility for user to unlock his account, when he tried to unlock the
account, behind the scene techincal user is unable to remove
pwdAccountLockedTime attribute and we receive Access Rights error.
We tried to switch Admin user but then it is contradicting with another
requirement of pwdHistory and user was able to reuse existing password during
password change https://issues.apache.org/jira/browse/DIRSERVER-2084
Is it possible to handle both requirements with one technical user? our
preference was to handle it with our own user instead of default admin
{code:java}
dn: cn=fdLdapAuthorizationRequirementsACISubentry,dc=abc,dc=xyz
changetype: add
objectclass: top
objectclass: subentry
objectclass: accessControlSubentry
cn: fdLdapAuthorizationRequirementsACISubentry
subtreeSpecification: {}
prescriptiveACI: {
identificationTag "directoryManagerFullAccessACI",
precedence 11,
authenticationLevel simple,
itemOrUserFirst userFirst:
{
userClasses
{
name { "uid=fdactmgr,ou=users,ou=system" }
},
userPermissions
{
{
protectedItems
{
entry, allUserAttributeTypesAndValues
},
grantsAndDenials
{
grantAdd, grantDiscloseOnError, grantRead,
grantRemove, grantBrowse, grantExport, grantImport,
grantModify, grantRename, grantReturnDN,
grantCompare, grantFilterMatch, grantInvoke
}
}
}
}
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2255) java.lang.OutOfMemoryError: Java heap space
[ https://issues.apache.org/jira/browse/DIRSERVER-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashid Mahmood updated DIRSERVER-2255: -- Attachment: image-2020-09-22-09-18-18-047.png > java.lang.OutOfMemoryError: Java heap space > --- > > Key: DIRSERVER-2255 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2255 > Project: Directory ApacheDS > Issue Type: Bug > Components: replication >Affects Versions: 2.0.0.AM25 > Environment: Linux CentOS 7 > Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) >Reporter: li >Priority: Major > Attachments: 1.png, 9-instances-SyncReplSearchListener .png, > conf.zip, image-2020-09-22-09-08-56-660.png, > image-2020-09-22-09-13-55-503.png, image-2020-09-22-09-18-18-047.png, > wrapper.conf > > > INFO | jvm 1| 2018/10/29 12:01:45 | Exception in thread "Thread-4" > java.lang.OutOfMemoryError: GC overhead limit exceeded > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.util.Arrays.copyOf(Arrays.java:3236) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.replaceWith(CharsetEncoder.java:301) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:207) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:233) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:558) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:554) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8.newEncoder(UTF_8.java:72) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.StringCoding.encode(StringCoding.java:348) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.String.getBytes(String.java:941) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.util.Strings.getBytesUtf8(Strings.java:1626) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.Value.(Value.java:261) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultAttribute.apply(DefaultAttribute.java:1828) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultEntry.readExternal(DefaultEntry.java:2443) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.ReplicaEventMessageSerializer.deserialize(ReplicaEventMessageSerializer.java:126) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:1188) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:81) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.recman.BaseRecordManager.fetch(BaseRecordManager.java:329) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.loadBPage(BPage.java:949) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.childBPage(BPage.java:938) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:380) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BTree.insert(BTree.java:302) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmTable.put(JdbmTable.java:541) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.ReplicaEventLog.log(ReplicaEventLog.java:176) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.SyncReplSearchListener.entryModified(SyncReplSearchListener.java:314) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.event.EventInterceptor.fire(EventInterceptor.java:169) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.event.EventInterceptor.modify(EventInterceptor.java:333) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:508) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.subtree.SubentryInterceptor.modify(SubentryInterceptor.java:1249) > INFO | jvm 1| 2018/10/29 12:01:47 | Exception in thread > "pool-13-thread-1"
[jira] [Commented] (DIRSERVER-2255) java.lang.OutOfMemoryError: Java heap space
[ https://issues.apache.org/jira/browse/DIRSERVER-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17199890#comment-17199890 ] Rashid Mahmood commented on DIRSERVER-2255: --- This is same problem as mentioned by [~jingwen.li] . I had only one consumer but i see many consumers under ou=system. *I also observed that when any error (e.g. transmission error) occurred during transfer of Entries as Intermediate Responses then a new consumer and repl-log is added in next iteration*. In Memory Repl Logs count grows and then comes OutOfMemoryException. As i mentioned we have to move forward to production system where replication is an important requirement, is there any quick and clean solution(without any manual deletion and restarts) to this problem? !image-2020-09-22-09-08-56-660.png!!image-2020-09-22-09-18-18-047.png! > java.lang.OutOfMemoryError: Java heap space > --- > > Key: DIRSERVER-2255 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2255 > Project: Directory ApacheDS > Issue Type: Bug > Components: replication >Affects Versions: 2.0.0.AM25 > Environment: Linux CentOS 7 > Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) >Reporter: li >Priority: Major > Attachments: 1.png, 9-instances-SyncReplSearchListener .png, > conf.zip, image-2020-09-22-09-08-56-660.png, > image-2020-09-22-09-13-55-503.png, image-2020-09-22-09-18-18-047.png, > wrapper.conf > > > INFO | jvm 1| 2018/10/29 12:01:45 | Exception in thread "Thread-4" > java.lang.OutOfMemoryError: GC overhead limit exceeded > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.util.Arrays.copyOf(Arrays.java:3236) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.replaceWith(CharsetEncoder.java:301) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:207) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:233) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:558) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:554) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8.newEncoder(UTF_8.java:72) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.StringCoding.encode(StringCoding.java:348) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.String.getBytes(String.java:941) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.util.Strings.getBytesUtf8(Strings.java:1626) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.Value.(Value.java:261) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultAttribute.apply(DefaultAttribute.java:1828) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultEntry.readExternal(DefaultEntry.java:2443) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.ReplicaEventMessageSerializer.deserialize(ReplicaEventMessageSerializer.java:126) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:1188) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:81) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.recman.BaseRecordManager.fetch(BaseRecordManager.java:329) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.loadBPage(BPage.java:949) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.childBPage(BPage.java:938) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:380) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BTree.insert(BTree.java:302) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmTable.put(JdbmTable.java:541) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.ReplicaEventLog.log(ReplicaEventLog.java:176) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.SyncReplSearchListener.entryModified(SyncReplSearchListener.java:314) > INFO | jvm 1|
[jira] [Commented] (DIRSERVER-2255) java.lang.OutOfMemoryError: Java heap space
[ https://issues.apache.org/jira/browse/DIRSERVER-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17199969#comment-17199969 ] Rashid Mahmood commented on DIRSERVER-2255: --- Thanks, on your website it is not mentioned that this part is experimental. It would be really helpful to make product decision if on ApacheDS Website it is explicilty stated what is production ready and what is experimental [https://directory.apache.org/apacheds/advanced-ug/5.4-replication.html] We have Java Based custom SSL Trust Management with many additional security checks, i dont think it would be easier to integrate them in OpenLDAP which is written in C. > java.lang.OutOfMemoryError: Java heap space > --- > > Key: DIRSERVER-2255 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2255 > Project: Directory ApacheDS > Issue Type: Bug > Components: replication >Affects Versions: 2.0.0.AM25 > Environment: Linux CentOS 7 > Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) >Reporter: li >Priority: Major > Attachments: 1.png, 9-instances-SyncReplSearchListener .png, > conf.zip, image-2020-09-22-09-08-56-660.png, > image-2020-09-22-09-13-55-503.png, image-2020-09-22-09-18-18-047.png, > wrapper.conf > > > INFO | jvm 1| 2018/10/29 12:01:45 | Exception in thread "Thread-4" > java.lang.OutOfMemoryError: GC overhead limit exceeded > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.util.Arrays.copyOf(Arrays.java:3236) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.replaceWith(CharsetEncoder.java:301) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:207) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:233) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:558) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:554) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8.newEncoder(UTF_8.java:72) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.StringCoding.encode(StringCoding.java:348) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.String.getBytes(String.java:941) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.util.Strings.getBytesUtf8(Strings.java:1626) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.Value.(Value.java:261) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultAttribute.apply(DefaultAttribute.java:1828) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultEntry.readExternal(DefaultEntry.java:2443) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.ReplicaEventMessageSerializer.deserialize(ReplicaEventMessageSerializer.java:126) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:1188) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:81) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.recman.BaseRecordManager.fetch(BaseRecordManager.java:329) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.loadBPage(BPage.java:949) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.childBPage(BPage.java:938) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:380) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BTree.insert(BTree.java:302) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmTable.put(JdbmTable.java:541) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.ReplicaEventLog.log(ReplicaEventLog.java:176) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.SyncReplSearchListener.entryModified(SyncReplSearchListener.java:314) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.event.EventInterceptor.fire(EventInterceptor.java:169) > INFO | jvm 1| 2018/10/29 12:01:45 | at >
[jira] [Updated] (DIRSERVER-2255) java.lang.OutOfMemoryError: Java heap space
[ https://issues.apache.org/jira/browse/DIRSERVER-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashid Mahmood updated DIRSERVER-2255: -- Attachment: image-2020-09-22-09-08-56-660.png > java.lang.OutOfMemoryError: Java heap space > --- > > Key: DIRSERVER-2255 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2255 > Project: Directory ApacheDS > Issue Type: Bug > Components: replication >Affects Versions: 2.0.0.AM25 > Environment: Linux CentOS 7 > Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) >Reporter: li >Priority: Major > Attachments: 1.png, 9-instances-SyncReplSearchListener .png, > conf.zip, image-2020-09-22-09-08-56-660.png, wrapper.conf > > > INFO | jvm 1| 2018/10/29 12:01:45 | Exception in thread "Thread-4" > java.lang.OutOfMemoryError: GC overhead limit exceeded > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.util.Arrays.copyOf(Arrays.java:3236) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.replaceWith(CharsetEncoder.java:301) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:207) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:233) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:558) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:554) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8.newEncoder(UTF_8.java:72) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.StringCoding.encode(StringCoding.java:348) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.String.getBytes(String.java:941) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.util.Strings.getBytesUtf8(Strings.java:1626) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.Value.(Value.java:261) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultAttribute.apply(DefaultAttribute.java:1828) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultEntry.readExternal(DefaultEntry.java:2443) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.ReplicaEventMessageSerializer.deserialize(ReplicaEventMessageSerializer.java:126) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:1188) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:81) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.recman.BaseRecordManager.fetch(BaseRecordManager.java:329) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.loadBPage(BPage.java:949) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.childBPage(BPage.java:938) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:380) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BTree.insert(BTree.java:302) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmTable.put(JdbmTable.java:541) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.ReplicaEventLog.log(ReplicaEventLog.java:176) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.SyncReplSearchListener.entryModified(SyncReplSearchListener.java:314) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.event.EventInterceptor.fire(EventInterceptor.java:169) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.event.EventInterceptor.modify(EventInterceptor.java:333) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:508) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.subtree.SubentryInterceptor.modify(SubentryInterceptor.java:1249) > INFO | jvm 1| 2018/10/29 12:01:47 | Exception in thread > "pool-13-thread-1" java.lang.OutOfMemoryError: GC overhead limit exceeded > INFO | jvm 1|
[jira] [Updated] (DIRSERVER-2255) java.lang.OutOfMemoryError: Java heap space
[ https://issues.apache.org/jira/browse/DIRSERVER-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashid Mahmood updated DIRSERVER-2255: -- Attachment: image-2020-09-22-09-13-55-503.png > java.lang.OutOfMemoryError: Java heap space > --- > > Key: DIRSERVER-2255 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2255 > Project: Directory ApacheDS > Issue Type: Bug > Components: replication >Affects Versions: 2.0.0.AM25 > Environment: Linux CentOS 7 > Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) >Reporter: li >Priority: Major > Attachments: 1.png, 9-instances-SyncReplSearchListener .png, > conf.zip, image-2020-09-22-09-08-56-660.png, > image-2020-09-22-09-13-55-503.png, wrapper.conf > > > INFO | jvm 1| 2018/10/29 12:01:45 | Exception in thread "Thread-4" > java.lang.OutOfMemoryError: GC overhead limit exceeded > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.util.Arrays.copyOf(Arrays.java:3236) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.replaceWith(CharsetEncoder.java:301) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:207) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:233) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:558) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:554) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8.newEncoder(UTF_8.java:72) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.StringCoding.encode(StringCoding.java:348) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.String.getBytes(String.java:941) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.util.Strings.getBytesUtf8(Strings.java:1626) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.Value.(Value.java:261) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultAttribute.apply(DefaultAttribute.java:1828) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultEntry.readExternal(DefaultEntry.java:2443) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.ReplicaEventMessageSerializer.deserialize(ReplicaEventMessageSerializer.java:126) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:1188) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:81) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.recman.BaseRecordManager.fetch(BaseRecordManager.java:329) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.loadBPage(BPage.java:949) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.childBPage(BPage.java:938) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:380) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BTree.insert(BTree.java:302) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmTable.put(JdbmTable.java:541) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.ReplicaEventLog.log(ReplicaEventLog.java:176) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.SyncReplSearchListener.entryModified(SyncReplSearchListener.java:314) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.event.EventInterceptor.fire(EventInterceptor.java:169) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.event.EventInterceptor.modify(EventInterceptor.java:333) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:508) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.subtree.SubentryInterceptor.modify(SubentryInterceptor.java:1249) > INFO | jvm 1| 2018/10/29 12:01:47 | Exception in thread > "pool-13-thread-1" java.lang.OutOfMemoryError: GC overhead
[jira] [Commented] (DIRSERVER-2255) java.lang.OutOfMemoryError: Java heap space
[ https://issues.apache.org/jira/browse/DIRSERVER-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1726#comment-1726 ] Rashid Mahmood commented on DIRSERVER-2255: --- It happens in our setup that TCP connection was reseted during Initial Refresh. But i noticed in subsequent connections Consumer did not send any cookie, therefore Server started new ReplicaId. When cookie is sent to consumer, is it sent after Initial Refresh finished? > java.lang.OutOfMemoryError: Java heap space > --- > > Key: DIRSERVER-2255 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2255 > Project: Directory ApacheDS > Issue Type: Bug > Components: replication >Affects Versions: 2.0.0.AM25 > Environment: Linux CentOS 7 > Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) >Reporter: li >Priority: Major > Attachments: 1.png, 9-instances-SyncReplSearchListener .png, > conf.zip, image-2020-09-22-09-08-56-660.png, > image-2020-09-22-09-13-55-503.png, image-2020-09-22-09-18-18-047.png, > wrapper.conf > > > INFO | jvm 1| 2018/10/29 12:01:45 | Exception in thread "Thread-4" > java.lang.OutOfMemoryError: GC overhead limit exceeded > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.util.Arrays.copyOf(Arrays.java:3236) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.replaceWith(CharsetEncoder.java:301) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:207) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:233) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:558) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:554) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8.newEncoder(UTF_8.java:72) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.StringCoding.encode(StringCoding.java:348) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.String.getBytes(String.java:941) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.util.Strings.getBytesUtf8(Strings.java:1626) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.Value.(Value.java:261) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultAttribute.apply(DefaultAttribute.java:1828) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultEntry.readExternal(DefaultEntry.java:2443) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.ReplicaEventMessageSerializer.deserialize(ReplicaEventMessageSerializer.java:126) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:1188) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:81) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.recman.BaseRecordManager.fetch(BaseRecordManager.java:329) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.loadBPage(BPage.java:949) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.childBPage(BPage.java:938) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:380) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BTree.insert(BTree.java:302) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmTable.put(JdbmTable.java:541) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.ReplicaEventLog.log(ReplicaEventLog.java:176) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.SyncReplSearchListener.entryModified(SyncReplSearchListener.java:314) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.event.EventInterceptor.fire(EventInterceptor.java:169) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.event.EventInterceptor.modify(EventInterceptor.java:333) > INFO | jvm 1| 2018/10/29 12:01:45 | at >
[jira] [Commented] (DIRSERVER-2255) java.lang.OutOfMemoryError: Java heap space
[
https://issues.apache.org/jira/browse/DIRSERVER-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17200162#comment-17200162
]
Rashid Mahmood commented on DIRSERVER-2255:
---
Is there any reason to set always ResultCodeEnum.SUCCESS from readResults()
method even in case of connection closed/request abandoned?
Because of this ResultCodeEnum.SUCCESS doInitialRefresh() will
* not call replicaLog.stop() and remove the listener
* add a new consumer
{code:java|title=SyncReplRequestHandler.java|borderStyle=solid}
private void readResults( LdapSession session, SearchRequest req, LdapResult
ldapResult,
Cursor cursor, long sizeLimit, ReplicaEventLog replicaLog )
throws Exception
{
long count = 0;
while ( ( count < sizeLimit ) && cursor.next() )
{
// Handle closed session
if ( session.getIoSession().isClosing() )
{
// The client has closed the connection
PROVIDER_LOG.debug( "Request terminated for message {}, the
client has closed the session",
req.getMessageId() );
break;
}
if ( req.isAbandoned() )
{
// The cursor has been closed by an abandon request.
PROVIDER_LOG.debug( "Request terminated by an AbandonRequest
for message {}", req.getMessageId() );
break;
}
Entry entry = cursor.get();
sendSearchResultEntry( session, req, entry, SyncStateTypeEnum.ADD );
String lastSentCsn = entry.get( csnAT ).getString();
replicaLog.setLastSentCsn( lastSentCsn );
count++;
}
PROVIDER_LOG.debug( "Sent {} entries for {}", count, replicaLog );
// DO NOT WRITE THE RESPONSE - JUST RETURN IT
ldapResult.setResultCode( ResultCodeEnum.SUCCESS );
if ( ( count >= sizeLimit ) && ( cursor.next() ) )
{
// We have reached the limit
// Move backward on the cursor to restore the previous position, as
we moved forward
// to check if there is one more entry available
cursor.previous();
// Special case if the user has requested more elements than the
request size limit
ldapResult.setResultCode( ResultCodeEnum.SIZE_LIMIT_EXCEEDED );
}
}
{code}
> java.lang.OutOfMemoryError: Java heap space
> ---
>
> Key: DIRSERVER-2255
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2255
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: replication
>Affects Versions: 2.0.0.AM25
> Environment: Linux CentOS 7
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
>Reporter: li
>Priority: Major
> Attachments: 1.png, 9-instances-SyncReplSearchListener .png,
> conf.zip, image-2020-09-22-09-08-56-660.png,
> image-2020-09-22-09-13-55-503.png, image-2020-09-22-09-18-18-047.png,
> wrapper.conf
>
>
> INFO | jvm 1| 2018/10/29 12:01:45 | Exception in thread "Thread-4"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> java.util.Arrays.copyOf(Arrays.java:3236)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> java.nio.charset.CharsetEncoder.replaceWith(CharsetEncoder.java:301)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> java.nio.charset.CharsetEncoder.(CharsetEncoder.java:207)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> java.nio.charset.CharsetEncoder.(CharsetEncoder.java:233)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> sun.nio.cs.UTF_8$Encoder.(UTF_8.java:558)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> sun.nio.cs.UTF_8$Encoder.(UTF_8.java:554)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> sun.nio.cs.UTF_8.newEncoder(UTF_8.java:72)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> java.lang.StringCoding.encode(StringCoding.java:348)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> java.lang.String.getBytes(String.java:941)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> org.apache.directory.api.util.Strings.getBytesUtf8(Strings.java:1626)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> org.apache.directory.api.ldap.model.entry.Value.(Value.java:261)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> org.apache.directory.api.ldap.model.entry.DefaultAttribute.apply(DefaultAttribute.java:1828)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> org.apache.directory.api.ldap.model.entry.DefaultEntry.readExternal(DefaultEntry.java:2443)
> INFO | jvm 1| 2018/10/29 12:01:45 | at
> org.apache.directory.server.ldap.replication.ReplicaEventMessageSerializer.deserialize(ReplicaEventMessageSerializer.java:126)
> INFO | jvm 1|
[jira] [Commented] (DIRSERVER-2255) java.lang.OutOfMemoryError: Java heap space
[ https://issues.apache.org/jira/browse/DIRSERVER-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17198396#comment-17198396 ] Rashid Mahmood commented on DIRSERVER-2255: --- We are facing same problem in Multi-Master setup in our Reference Env. Next target is our production environment We have 2 seperate data centers backed by load balancer. Each data center has a Maste-Slave(Machine1 Master and Machine 2 slave) setup with 20k enrtries. We need a Master-Master setup between Data Centers, i enabled the consumer on each Data Center's Master instance to poll the other Data Center's Master instance. Those Master instances had already 20K Entries. Then i noticed Replication was not working, any change made on one Master is not replicated on other Master. Memory usage on each Master was reaching to 2GB. Took a heap dump on one instance and found SyncReplSearchListener occupied almost 90% of memory. What could be the reason??? Couple of more questions: 1). Are both Masters trying to synch all entries? I think so maybe because both newly enabled consumers on each Master are not sending any cookie to the target Master, it makes Master think of sending all entries to consumer. 2). How many consumers one Master can serve, is there any benchmark? 3). Is there any guideline with best practices in setting up Multi-Master for Production System? 4). We have a cron job which makes daily backup of our Data Partition, in case of broken DB on one Master/Slave; should we restore from backup or just create a fresh installation? To make restore with minimun Repk overhead we need to make backup of the cookie entry so that Repl-Server send only those modifications which happend after DB corruption, right??? Our Environment: Linux Centos 7 ApacheDS 2.0.0.AM24 All consumers are with ads-replrefreshnpersist: TRUE configured. !9-instances-SyncReplSearchListener .png! > java.lang.OutOfMemoryError: Java heap space > --- > > Key: DIRSERVER-2255 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2255 > Project: Directory ApacheDS > Issue Type: Bug > Components: replication >Affects Versions: 2.0.0.AM25 > Environment: Linux CentOS 7 > Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) >Reporter: li >Priority: Major > Attachments: 1.png, 9-instances-SyncReplSearchListener .png, > conf.zip, wrapper.conf > > > INFO | jvm 1| 2018/10/29 12:01:45 | Exception in thread "Thread-4" > java.lang.OutOfMemoryError: GC overhead limit exceeded > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.util.Arrays.copyOf(Arrays.java:3236) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.replaceWith(CharsetEncoder.java:301) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:207) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:233) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:558) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:554) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8.newEncoder(UTF_8.java:72) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.StringCoding.encode(StringCoding.java:348) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.String.getBytes(String.java:941) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.util.Strings.getBytesUtf8(Strings.java:1626) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.Value.(Value.java:261) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultAttribute.apply(DefaultAttribute.java:1828) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultEntry.readExternal(DefaultEntry.java:2443) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.ReplicaEventMessageSerializer.deserialize(ReplicaEventMessageSerializer.java:126) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:1188) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:81) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.recman.BaseRecordManager.fetch(BaseRecordManager.java:329) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.loadBPage(BPage.java:949) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.childBPage(BPage.java:938) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:380) > INFO
[jira] [Updated] (DIRSERVER-2255) java.lang.OutOfMemoryError: Java heap space
[ https://issues.apache.org/jira/browse/DIRSERVER-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashid Mahmood updated DIRSERVER-2255: -- Attachment: 9-instances-SyncReplSearchListener .png > java.lang.OutOfMemoryError: Java heap space > --- > > Key: DIRSERVER-2255 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2255 > Project: Directory ApacheDS > Issue Type: Bug > Components: replication >Affects Versions: 2.0.0.AM25 > Environment: Linux CentOS 7 > Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) >Reporter: li >Priority: Major > Attachments: 1.png, 9-instances-SyncReplSearchListener .png, > conf.zip, wrapper.conf > > > INFO | jvm 1| 2018/10/29 12:01:45 | Exception in thread "Thread-4" > java.lang.OutOfMemoryError: GC overhead limit exceeded > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.util.Arrays.copyOf(Arrays.java:3236) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.replaceWith(CharsetEncoder.java:301) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:207) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.nio.charset.CharsetEncoder.(CharsetEncoder.java:233) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:558) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8$Encoder.(UTF_8.java:554) > INFO | jvm 1| 2018/10/29 12:01:45 | at > sun.nio.cs.UTF_8.newEncoder(UTF_8.java:72) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.StringCoding.encode(StringCoding.java:348) > INFO | jvm 1| 2018/10/29 12:01:45 | at > java.lang.String.getBytes(String.java:941) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.util.Strings.getBytesUtf8(Strings.java:1626) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.Value.(Value.java:261) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultAttribute.apply(DefaultAttribute.java:1828) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.api.ldap.model.entry.DefaultEntry.readExternal(DefaultEntry.java:2443) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.ReplicaEventMessageSerializer.deserialize(ReplicaEventMessageSerializer.java:126) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:1188) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.deserialize(BPage.java:81) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.recman.BaseRecordManager.fetch(BaseRecordManager.java:329) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.loadBPage(BPage.java:949) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.childBPage(BPage.java:938) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:380) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BPage.insert(BPage.java:381) > INFO | jvm 1| 2018/10/29 12:01:45 | at > jdbm.btree.BTree.insert(BTree.java:302) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmTable.put(JdbmTable.java:541) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.ReplicaEventLog.log(ReplicaEventLog.java:176) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.ldap.replication.provider.SyncReplSearchListener.entryModified(SyncReplSearchListener.java:314) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.event.EventInterceptor.fire(EventInterceptor.java:169) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.event.EventInterceptor.modify(EventInterceptor.java:333) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:508) > INFO | jvm 1| 2018/10/29 12:01:45 | at > org.apache.directory.server.core.subtree.SubentryInterceptor.modify(SubentryInterceptor.java:1249) > INFO | jvm 1| 2018/10/29 12:01:47 | Exception in thread > "pool-13-thread-1" java.lang.OutOfMemoryError: GC overhead limit exceeded > INFO | jvm 1| 2018/10/29 12:01:47 | at >
