Problem with closing environment

Question

We ran into a problem where our Environments were not closing properly. After a bit of inspection, we found there was a ConcurrentModificationException being thrown and eaten in the Environment.close() method during the referring database cleanup:
       Iterator iter = referringDbs.iterator();
       while (iter.hasNext()) {
                        Database db = (Database) iter.next();
                         * Save the db name before we attempt the close, it's
                         * unavailable after the close.
                        String dbName = db.getDebugName();
                        errors.append(dbName).append(" ");
                        try {
                            db.close();
                        } catch (RunRecoveryException e) {
                            throw e;
                        } catch (DatabaseException DBE) {
                            errors.append("\nWhile closing Database ");
                            errors.append(dbName);
                            errors.append(" encountered exception: ");
                            errors.append(DBE).append("\n");
                    }The referringDbs set is being changed during the close process, invalidating the iterator -> db.close () calls Database.close() which calls closeInternal() which calls back to Environment.removeReferringHandle() which has this line in it: referringDbs.remove(db);
So once the ConcurrentModificationException is thrown, the finally block inside of Environment.close replaces that exception by throwing a new DatabaseException with the "There are 3 open database in the Environment..." message:
            if (errors.length() > 0) {
                throw new DatabaseException(errors.toString());
            }So we are looking for help/info in two areas:
1) The condition causing the ConcurrentModificationException
2) When an exception other than RunRecoveryException and DatabaseException are thrown in Environment.close(), it would be desirable if the message was propagated up in some way
Thanks

Answer 1

Thanks for the report Erik. I suspect you are not closing all the Database handles that you have opened against the Environment that you are closing and that if you do, this problem will go away. Let me know if that workaround works for you.
I'll work on a fix for this, but it probably won't be incorporated until the next release.
Charles Lamb