kodo.util.FatalUserException: kodo.util.FatalUserException: The PersistenceManager has been closed. The stack trace at which the PersistenceManager was closed is held in the embedded exception. NestedThrowables: kodo.util.UserException: NestedThrowables: kodo.util.UserException:

Oracle Community | 3004 | 1 decade ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    3.0.0RC2 weird behavior

    Oracle Community | 1 decade ago | 3004
    kodo.util.FatalUserException: kodo.util.FatalUserException: The PersistenceManager has been closed. The stack trace at which the PersistenceManager was closed is held in the embedded exception. NestedThrowables: kodo.util.UserException: NestedThrowables: kodo.util.UserException:

    Root Cause Analysis

    1. kodo.util.FatalUserException

      kodo.util.FatalUserException: The PersistenceManager has been closed. The stack trace at which the PersistenceManager was closed is held in the embedded exception. NestedThrowables: kodo.util.UserException: NestedThrowables: kodo.util.UserException:

      at kodo.util.FatalUserException.writeReplace()
    2. kodo.util
      FatalUserException.writeReplace
      1. kodo.util.FatalUserException.writeReplace(FatalUserException.java:74)
      1 frame
    3. Java RT
      ObjectOutputStream.writeObject
      1. java.io.ObjectStreamClass.invokeMethod(ObjectStreamClass.java:1610)
      2. java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298)
      2 frames
    4. weblogic.common.internal
      ChunkedObjectOutputStream.writeObject
      1. weblogic.common.internal.ChunkedObjectOutputStream.writeObject(ChunkedObjectOutputStream.java:107)
      1 frame