directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Selcuk AYA <>
Subject Re: Replication reboot test failure : headsup
Date Sat, 03 Sep 2011 07:31:27 GMT
On Fri, Sep 2, 2011 at 3:31 AM, Emmanuel Lecharny <> wrote:
> Hi guys,
> finally, I found the reason why this test was failing :
> the SyncInfoValue is not a control, but a part of the IntermediateMessage.
> It's value is stored into the IntermediateMessage value, and should be
> decoded locally. It was the case a while back
> (,
> but it was replaced by some code assuming the SyncInfoValue was a control.
> There was also another problem: the ads-repl ookie AT is an operatioanl
> attribute, and the lookup we did was'nt returning it. This has been fixed.
> I have added a CONSUMER_LOG logger to help the analysis of replication. We
> now have PROUCER_LOG for the producer and the same for the consumer.
> Understanding what's going on at both side should be easier. (even f right
> now, we don't have enough logs).
> Sadly, the reboot test seems to fail randomly. In Eclipse, I have it working
> but it fails from time to time. It seems that we have some timing issue,
> somewhere. If I set the logs, it does not fail anymore.

In my case these random failures were caused by failures during
deserialization while reading from the event log. I created
DIRSERVER-1653 and attached a diff that fixes the issue. Please try
that patch. After this fix, testReboot passed both in eclipse and
maven for me.

> I will crash, after having committed the fixes. The test will be @Ignored.
> I'll work o this issue tomorrow.
> FYI, I also injected Selcuk's branch (apacheds-jdbm) into trunks.
> --
> Regards,
> Cordialement,
> Emmanuel L├ęcharny


View raw message