Internal Error while repeatedly querying

Question

I’m having a problem when I try to repeatedly query the Berkley XML DB. I’m using XML DB 2.3.8 on Windows and Java 1.4.2_13.
Typically my first 2000 or so queries will work, and then they will begin to fail with the following exception.
com.sleepycat.dbxml.XmlException: std::exception thrown from C++ API: bad allocation, errcode = INTERNAL_ERROR
     at com.sleepycat.dbxml.dbxml_javaJNI.XmlManager_query__SWIG_2(Native Method)
     at com.sleepycat.dbxml.XmlManager.query(XmlManager.java:606)
I assume the problem is that I’m not setting something up properly or not cleaning up objects after each query. I was hoping someone could tell me what the exception could be caused by and what I should check my code for.
If it helps my code basically does the following:
During initialization open an environment
For each query
1)     open container
2)     Create an XmlQueryContext
3)     Obtain an XmlResults object by calling XmlManager.query(String, XmlQueryContext)
4)     Obtain an XmlValue by calling XmlResults.next()
5)     Obtain an XmlDocument by calling XmlValue.asDocument()
6)     Call XmlContainer.delete()
7)     Call XmlQueryContext.delete()
8)     Call XmlResults.delete()
9)     Call XmlValue.delete()
10)     Call XmlDocument.delete()
My environment is being opened with the following parameters:
EnvironmentConfig config = new EnvironmentConfig();
config.setCacheSize(50 * 1024 * 1024);
config.setMaxLockers(100000);
config.setMaxLockObjects(100000);
config.setMaxLocks(100000);
config.setAllowCreate(true);
config.setInitializeCache(true);
config.setTransactional(true);
config.setInitializeLocking(true);
config.setInitializeLogging(true);
config.setAllowCreate(true);
config.setErrorStream(System.err);
//config.setRunFatalRecovery(true);
config.setRunRecovery(true);
The container is being opened with the following parameters:
XmlContainerConfig config = new XmlContainerConfig();
config.setTransactional(true);
config.setAllowCreate(true);
Thanks,
Eric

Answer 1

Hi Eric,
You will probably need to delete each XmlValue and XmlDocument in the loop before getting a new one. I expect this is why you are seeing odd errors, which are almost certainly out of memory issues.
John