Hi,
I am trying to reproduce the problem (with 1000 child nodes), but so
far I couldn't find a problem. This could have two reasons:
A) Are you sure you cleaned the repository between tests?
B) The method initializeContractor.
Could you please send your code for initializeContractor?
I used:
static void initializeContractor(Session session, Node contractor)
throws Exception {
contractor.setProperty("name", "Hello");
}
After testOneByOne I have:
SELECT COUNT(*) FROM default_binval: 0
SELECT COUNT(*) FROM default_node: 1003
SELECT COUNT(*) FROM default_prop: 2003
SELECT COUNT(*) FROM default_refs: 0
SELECT COUNT(*) FROM version_binval: 0
SELECT COUNT(*) FROM version_node: 1
SELECT COUNT(*) FROM version_prop: 1
SELECT COUNT(*) FROM version_refs: 0
After testBatch I have:
SELECT COUNT(*) FROM default_binval: 0
SELECT COUNT(*) FROM default_node: 1003
SELECT COUNT(*) FROM default_prop: 2003
SELECT COUNT(*) FROM default_refs: 0
SELECT COUNT(*) FROM version_binval: 0
SELECT COUNT(*) FROM version_node: 1
SELECT COUNT(*) FROM version_prop: 1
SELECT COUNT(*) FROM version_refs: 0
So, no difference.
Thanks,
Thomas
On 6/20/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 6/20/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> This seems more related to how the MySQL persistence manager handles
> constant updates of a shared parent nodes with more and more child nodes.
> Also your use of same name sibblings might be an issue, actually.
This sounds like it could be a problem in how same name siblings are
handled in NodeState. If this is the case and someone can further
qualify the issue and fix it in a short timeframe, I would very much
like to have the fix included in 1.3.1.
BR,
Jukka Zitting
