org.hibernate.AssertionFailure: null id in implementationrequests.BadcockSystems entry (don't flush the Session after exception occurs)

Stack Overflow | Parth | 8 months 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

    org.hibernate.AssertionFailure: null id in domain entry (don't flush the session after exception occurs) after grails upgradation to 2.0.4

    Stack Overflow | 8 months ago | Parth
    org.hibernate.AssertionFailure: null id in implementationrequests.BadcockSystems entry (don't flush the Session after exception occurs)
  2. 0

    Grails User (Old Archive) - Grails Noob - AssertionFailure: null id

    nabble.com | 1 year ago
    org.hibernate.AssertionFailure: null id in objecteo.ms.SalesOrderMaterial entry (don't flush the Session after an exception occurs) at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:603)

    Root Cause Analysis

    1. org.hibernate.AssertionFailure

      null id in implementationrequests.BadcockSystems entry (don't flush the Session after exception occurs)

      at impelementationrequests.BadcockSystemsController$_closure4.doCall()
    2. impelementationrequests
      BadcockSystemsController$_closure4.doCall
      1. impelementationrequests.BadcockSystemsController$_closure4.doCall(BadcockSystemsController.groovy:24)
      1 frame
    3. Java RT
      Thread.run
      1. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      2. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      3. java.lang.Thread.run(Thread.java:745)
      3 frames