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

Oracle Community | 473555 | 1 decade ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards 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_createContainer__SWIG_0()
    2. com.sleepycat.dbxml
      dbxml_javaJNI.XmlManager_createContainer__SWIG_0
      1. com.sleepycat.dbxml.dbxml_javaJNI.XmlManager_createContainer__SWIG_0(Native Method)
      1 frame