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

Oracle Community | 473555 | 10 years ago
  1. 0

    Problem after update to 2.3.8

    Oracle Community | 10 years ago | 473555
    com.sleepycat.dbxml.XmlException: null object - call after object destroyed?, errcode = INTERNAL_ERROR
  2. 0

    Problem after update to 2.3.8

    Oracle Community | 10 years ago | 473555
    com.sleepycat.dbxml.XmlException: null object - call after object destroyed?, errcode = INTERNAL_ERROR
  3. 0

    Problem after update to 2.3.8

    Oracle Community | 10 years ago | 473555
    com.sleepycat.dbxml.XmlException: null object - call after object destroyed?, errcode = INTERNAL_ERROR
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Problem after update to 2.3.8

    Oracle Community | 10 years ago | 473555
    com.sleepycat.dbxml.XmlException: null object - call after object destroyed?, errcode = INTERNAL_ERROR
  6. 0

    Segmentation Fault

    Oracle Community | 7 years ago | 700448
    com.sleepycat.dbxml.XmlException: Error: A null XmlValue object cannot be added to the result set., errcode = INV ALID_VALUE

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    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