kodo.util.OptimisticVerificationException: An optimistic lock violation was detected when flushing object instance "net.inar.cim.reclamos.domain.DetalleStock-8316" to the data store. This indicates that the object was concurrently modified in another transaction.[net.inar.cim.reclamos.domain.DetalleStock-8316]

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

    Attach problem with mySql

    Oracle Community | 1 decade ago | 3004
    kodo.util.OptimisticVerificationException: An optimistic lock violation was detected when flushing object instance "net.inar.cim.reclamos.domain.DetalleStock-8316" to the data store. This indicates that the object was concurrently modified in another transaction.[net.inar.cim.reclamos.domain.DetalleStock-8316]

    Root Cause Analysis

    1. kodo.util.OptimisticVerificationException

      An optimistic lock violation was detected when flushing object instance "net.inar.cim.reclamos.domain.DetalleStock-8316" to the data store. This indicates that the object was concurrently modified in another transaction.[net.inar.cim.reclamos.domain.DetalleStock-8316]

      at kodo.runtime.AttachManager.attach()
    2. kodo.runtime
      PersistenceManagerImpl.attach
      1. kodo.runtime.AttachManager.attach(AttachManager.java:373)
      2. kodo.runtime.AttachManager.attachCollection(AttachManager.java:633)
      3. kodo.runtime.AttachManager.attachField(AttachManager.java:537)
      4. kodo.runtime.AttachManager.attach(AttachManager.java:338)
      5. kodo.runtime.AttachManager.attachField(AttachManager.java:522)
      6. kodo.runtime.AttachManager.attach(AttachManager.java:338)
      7. kodo.runtime.AttachManager.attach(AttachManager.java:55)
      8. kodo.runtime.PersistenceManagerImpl.attach(PersistenceManagerImpl.java:3963)
      8 frames