INTERNAL_ERROR in multithreaded test on db xml 2.3.10

Question

I upgraded from 2.2.13 to 2.3.10. I'm on Windows XP / Java 1.5.10
My multi-threaded test soon hits INTERNAL_ERRORs when running on 2.3.10.
While on 2.2.13, I have much better results.
My test case basically sets up one or more threads doing a tight loop of
for (i=1; i < 10000000; i++) {
  try { putXML("key"+i/2, contentString); } finally {}
  try {getXML("key+i/2); } finally {}
}With one thread, this test will run for at least an hour or more until my time limit expires.
With two threads, this will run ~10-20 minutes
With three threads this test will immediately hit these internal errors.
Once these errors, they repeat and soon the JVM crashes.
I've checked nearly every forum posting, deleted every results.next, deleted every Xml* object possible (except XmlContainer) and so on.
Any advice? Are there any samples that do multi-threaded write/read/queries?
Are there any clues to be found by looking at com.sleepycat.dbxml.dbxml_javaJNI.XmlContainer_putDocument__SWIG_12 ?
Thanks in advance,
Douglas Moore
Reported error:
com.sleepycat.dbxml.XmlException: Uncaught exception from C++ API, errcode = INTERNAL_ERROR
at com.sleepycat.dbxml.dbxml_javaJNI.XmlContainer_putDocument__SWIG_12(Native Method)
at com.sleepycat.dbxml.XmlContainer.putDocument(XmlContainer.java:433)
at  ....putXML(XMLBDBFacade.java:370)create container method:
       // set properties specific to the BDB XML Container
        XmlContainerConfig xmlContainerConfig = new XmlContainerConfig();
        xmlContainerConfig.setAllowCreate(true);
        // TODO review me this is new for BDB XML 2.3.10
        // TODO review me xmlContainerConfig.setDirtyRead(BDB_XML_DIRTY_READ);
        xmlContainerConfig.setMultiversion(true);
        xmlContainerConfig.setSnapshot(true);
        xmlContainerConfig.setReadUncommitted(false);
        xmlContainerConfig.setTransactional(true);
        //TODO xmlContainerConfig.setPageSize(1024);
        xmlContainerConfig.setAllowValidation(false);
        xmlContainerConfig.setNodeContainer(true);
        xmlContainerConfig.setIndexNodes(true);
        xmlContainerConfig.setCacheSize(200000);
        xmlContainerConfig.setCacheCount(1);
        if (LOG.isDebugEnabled()) {
            LOG.debug("Creating XML DB Container "
                    + dpcContainerConfig$.getAbsolutePath());
        // BDB XML container create
        XmlContainer xmlContainer = getBDBXMLManager().openContainer(
            dpcContainerConfig$.getAbsolutePath(),
            xmlContainerConfig);getXmlTransaction method:
            TransactionConfig txnConfig = new TransactionConfig();
            txnConfig.setNoWait(true);
            txnConfig.setReadUncommitted(true);
            txnConfig.setReadCommitted(true);
            txnConfig.setSnapshot(true);
            txnConfig.setSync(true);
            transaction = getXmlManager().createTransaction(null, txnConfig);putXML method:
        try {
            ContentKey contentKey = new ContentKey(container$, key$, ContentType.XML);
            boolean exists = ItemRegistry.instance().contains(contentKey);
            if (exists) {
                // updating document
                doc = getXmlManager().createDocument();
                doc.setName(key$);
                doc.setContent(content$);
                updateContext = getXmlManager().createUpdateContext();
                xmlContainer.updateDocument(transaction$, doc, updateContext);
            } else {
                // putting document
                updateContext = getXmlManager().createUpdateContext();
                xmlContainer.putDocument(transaction$, key$, content$, updateContext);
                ItemRegistry.instance().add(contentKey);
        } catch (XmlException e) {
                BDBUtility.handleXmlException(container$, key$, e);
        } finally {
            if (null != doc) {
                doc.delete();
                doc = null;
            if (null != updateContext) {
                updateContext.delete();
                updateContext = null;
            }

Answer 1

Yes, we have the same error:
com.sleepycat.dbxml.XmlException: std::exception thrown from C++ API: bad allocation: Unknown error, errcode = INTERNAL_ERROR
     at com.sleepycat.dbxml.dbxml_javaJNI.XmlQueryExpression_execute__SWIG_1(Native Method)
     at com.sleepycat.dbxml.XmlQueryExpression.execute(XmlQueryExpression.java:93)
com.sleepycat.dbxml.XmlException, errcode = NO_MEMORY_ERROR
     at com.sleepycat.dbxml.dbxml_javaJNI.XmlQueryExpression_execute__SWIG_1(Native Method)
     at com.sleepycat.dbxml.XmlQueryExpression.execute(XmlQueryExpression.java:93)
The version we use is 2.2.13, can anyone give suggestions to resolve it?
Regards,
Jane