I've just run into a similar problem. I looked into the code and it
appears that the Collection.close() method is essentially a no-op (does
nothing but return true). Does this in fact mean that all of these
collection files are not being closed or am I missing something? I
thought maybe the dispose() method would do more, but it simply calls
the close() method. This would corroberate my observations that I have
to kill my JVM to clean up these open files.
Peter
-----Original Message-----
From: David J. Thomson [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2003 1:05 PM
To: xindice-users@xml.apache.org
Cc: [EMAIL PROTECTED]
Subject: Collection numbers: Here's what's going on
Hello all,
First of all, I'm surprised other people haven't run into this kind of
problem. I have one collection with about 95 subcollections, each of which
has four subcollections. It kills my system after a little while because it
runs out of file descriptors. Java gives all sorts of errors about having
too many open files, after I've already increased the number to Linux's
system max of 1048576. Not only that, but on another occasion, it somehow
corrupted the database when I ran out of file descriptors, which was making
it appear as though the problem was something else. I thought there was a
concurrency problem because one of the collections was corrupted, but it
appears as though this is it. Has anyone else dealt with this? Can I please
take a poll of how many collections people have and how many documents in
each. I mean, most databases can handle hundreds of thousands of records for
tables, so I don't know what to do here.
Thanks,
David
