com.sleepycat.dbxml.XmlException: null object - call after object destroyed?, errcode = INTERNAL_ERROR

Oracle Community | 473555 | 1 decade ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    Problem after update to 2.3.8

    Oracle Community | 1 decade ago | 473555
    com.sleepycat.dbxml.XmlException: null object - call after object destroyed?, errcode = INTERNAL_ERROR

    Root Cause Analysis

    1. com.sleepycat.dbxml.XmlException

      null object - call after object destroyed?, errcode = INTERNAL_ERROR

      at com.sleepycat.dbxml.dbxml_javaJNI.XmlManager_createTransaction()
    2. com.sleepycat.dbxml
      dbxml_javaJNI.XmlManager_createTransaction
      1. com.sleepycat.dbxml.dbxml_javaJNI.XmlManager_createTransaction(Native Method)
      1 frame