Fwd: New directory server release?
I forgot to answer to the ML… -- Message transféré - De : Emmanuel Lecharny Date : jeu. 14 juil. 2022 à 15:05 Objet : Re: New directory server release? À : Hi Colm, I really would like to get Mina 2.2.0 included. This version is currently being voted, so my guess is that it may be available next week. Once done, yes, a release would be appropriate. Le jeu. 14 juil. 2022 à 09:39, Colm O hEigeartaigh a écrit : > Hi, > > There have been quite a few fixes for the directory server > (https://issues.apache.org/jira/projects/DIRSERVER/versions/12343914) > since the last release, which was over 2 years ago, not to mention > third-party dependency security upgrades. > > Are there any major blockers to cutting a new release? Otherwise IMO > we might consider moving it to the attic, and focusing on Studio/API > and the smaller subprojects. > > Colm. > > - > To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org > For additional commands, e-mail: dev-h...@directory.apache.org > > -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re: New directory server release?
> On Jul 14, 2022, at 2:38 AM, Colm O hEigeartaigh wrote: > > Are there any major blockers to cutting a new release? Otherwise IMO > we might consider moving it to the attic, and focusing on Studio/API > and the smaller subprojects. Well this gets to having someone who can maintain the code. Since I’ve been on the project that responsibility has fallen on Emmanuel. My assumption is he’s been busy but hasn’t stepped away. This puts a timer on the coming back part. How long do we wait? I think if its important enough to continue with the directory, we should wait a bit longer. It also puts up a call to the users. Is the Apache Directory server still important to you? How important - are you willing to step up and grab a shovel? — Shawn - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2341) Apache DS stops serving requests after error
[
https://issues.apache.org/jira/browse/DIRSERVER-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated DIRSERVER-2341:
---
Fix Version/s: (was: 2.0.0.AM26)
> Apache DS stops serving requests after error
>
>
> Key: DIRSERVER-2341
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2341
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: jdbm
>Affects Versions: 2.0.0.AM26
> Environment: Apache DS 2.0.0 AM 26 running over RHEL 7.8 and Oracle
> JDK 1.8.0_241-b07.
>Reporter: Andrea Campana
>Priority: Major
> Labels: ERR_554, bug
>
> 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:
>
> @
>
> {code:java}
> [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)
>
> {code}
>
>
> {{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}}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2364) How to ApacheDS Sync with Active Directory
[ https://issues.apache.org/jira/browse/DIRSERVER-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRSERVER-2364: --- Fix Version/s: (was: 2.0.0.AM26) > How to ApacheDS Sync with Active Directory > -- > > Key: DIRSERVER-2364 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2364 > Project: Directory ApacheDS > Issue Type: Improvement > Components: migration >Affects Versions: 2.0.0.AM26 >Reporter: pasit chatcharoenkit >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
New directory server release?
Hi, There have been quite a few fixes for the directory server (https://issues.apache.org/jira/projects/DIRSERVER/versions/12343914) since the last release, which was over 2 years ago, not to mention third-party dependency security upgrades. Are there any major blockers to cutting a new release? Otherwise IMO we might consider moving it to the attic, and focusing on Studio/API and the smaller subprojects. Colm. - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
