Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com
 designates 74.125.82.53 as permitted sender)
Message-ID: <527F5125.2030106@gmail.com>
Date: Sun, 10 Nov 2013 10:25:57 +0100
From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= <elecharny@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Ads + Mavibot Partition
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Just  quick heads up :

Im tryinh to fix a bug that forbid us to inject a few thousands entries
in the server (the injection test fails after aound 3000 thousands of
entries added). The problem lies in teh way we serialize/deserialize
ParentIdAndRdn. For some reason, we add the length of the byte[]
containing the ParentIdAndRdn before the serialized value. The
deserializer does not expect to find this length, thought the next
position is not good. If I remove this length, now I have a pb because
the number of expected RDNs is too big, and I get an
ArrayOutofCoundException while tryingt to create an array of RDN[] with
zillions of values.

Obviously, we don't serialize/deserialize correctly, although the
ser/deser methods have been tested and work. It's more about the way we
call them : when we reach a number of stored elements, the cache is
full, and we need to read back some pages from disk. This is when we
have the issue. I have to understand why a Page deserialization fails.
It should not be such a big issue, but the failure is quite random
(something I don't understand, though... Not sure that the cache is not
responsible for this randomness).

I'll keep the list updated.

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com