I have few details yet, but have a report from a user upgrading from 10.5 to 10.8 who is reporting occurrences of IOException too many open files on both linux and windows in their test suite after the upgrade. The actual error is not usually in the Derby code but it may be that Derby is hogging too many files causing this failure later in their code.

They can reproduce the problem in a 15 minute test. Is there a generic java or operating system way to trace the opening and closing of files? If not, what would be the best place to add tracing to Derby?

Thanks

Kathey


Reply via email to