Bug in 2.5.13 Java XmlValue.getAttributes()

Question

There seems to be some issue with properly deleting the XmlResults from XmlValue.getAttributes() using the Java api. Here is a sample function to illustrate the issue:
private static void runAQuery(XmlManager manager, String query) {
                System.out.println("Running query: "+query);
                XmlResults queryRes = null;
                try {
                        final XmlQueryContext qc =
                                manager.createQueryContext(XmlQueryContext.LiveValues, XmlQueryContext.Lazy);
                        queryRes = manager.query(query, qc);
                        XmlValue temp;
                        while(queryRes.hasNext()) {
                                temp = queryRes.next();
                                XmlResults attrRes = temp.getAttributes();
                                XmlValue t = attrRes.next();
                                System.out.println("Saw attr name: "+t.getNodeName());
                                attrRes.delete();
                } catch(XmlException e) {
                        e.printStackTrace();
                } finally {
                        if(queryRes != null) {
                                queryRes.delete();
        }Running this produces:
Running query: (collection('db.dbxml')/scenario)[1]
Saw attr name: name
com.sleepycat.dbxml.XmlException: null object - call after object destroyed?, errcode = INVALID_VALUE
     at com.sleepycat.dbxml.dbxml_javaJNI.XmlResults_hasNext(Native Method)
     at com.sleepycat.dbxml.XmlResults.hasNext(XmlResults.java:142)
     at test.runAQuery(test.java:41)
     at test.main(test.java:24)So it seemed maybe I should not delete the attribute results however if I comment out:
                                //attrRes.delete();and see what what happens, I get:
Running query: (collection('db.dbxml')/scenario)[1]
Saw attr name: name
Database handles still open at environment close
Open database handle: db.dbxml/structural_stats
Open database handle: db.dbxml/secondary_document_statistics_double
Open database handle: db.dbxml/secondary_document_index_double
Open database handle: db.dbxml/secondary_document_statistics_string
Open database handle: db.dbxml/secondary_document_index_string
Open database handle: db.dbxml/node_nodestorage
Open database handle: db.dbxml/secondary_document
Open database handle: db.dbxml/secondary_dictionary
Open database handle: db.dbxml/primary_dictionary
Open database handle: db.dbxml/secondary_sequence
Open database handle: db.dbxml/secondary_configuration
Exception in thread "main" java.lang.IllegalArgumentException: Invalid argument
     at com.sleepycat.db.internal.db_javaJNI.DbEnv_close0(Native Method)
     at com.sleepycat.db.internal.DbEnv.close0(DbEnv.java:268)
     at com.sleepycat.db.internal.DbEnv.close(DbEnv.java:79)
     at com.sleepycat.db.Environment.close(Environment.java:141)
     at com.sleepycat.dbxml.XmlManager.closeInternal(XmlManager.java:418)
     at com.sleepycat.dbxml.XmlManager.delete(XmlManager.java:35)
     at com.sleepycat.dbxml.XmlManager.close(XmlManager.java:427)
     at test.main(test.java:31)Thanks,
Pralit

Answer 1

I concur. I can also see such a bug in DB XML 2.5. :(( Probably closing of the attrRes object implicitly causes closing of the queryRes object (partially?). One hack solution would be to keep all atrrRes objects somewhere and close them together with queryRes objects.
Vyacheslav