Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11213

On release of batch it still contained JDBC statements logged

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 14.0.1.Final
    • JPA / Hibernate
    • None
    • Hide

      I initially took this to hibernate (https://discourse.hibernate.org/t/on-release-of-batch-it-still-contained-jdbc-statements/1540/3) but was unable to get this to trigger with their simple test cases. Hibernate has suggested this is an integration issue with wildfly.

      I have instead created a demo EE8 project which reproduces it.

      https://github.com/codylerum/demos/tree/master/jpa-batch-release

      Deploy, and browse to http://localhost:8080/demo and click execute you will see the log messages.

      Show
      I initially took this to hibernate ( https://discourse.hibernate.org/t/on-release-of-batch-it-still-contained-jdbc-statements/1540/3 ) but was unable to get this to trigger with their simple test cases. Hibernate has suggested this is an integration issue with wildfly. I have instead created a demo EE8 project which reproduces it. https://github.com/codylerum/demos/tree/master/jpa-batch-release Deploy, and browse to http://localhost:8080/demo and click execute you will see the log messages.

      After updating from Wildfly 11 (Hibernate 5.1.10) to Wildfly 14.0.1 (Hibernate 5.3.6) I've started seeing the following log messages

      I’m starting to see the log message

      2018-10-17 20:12:47,571 INFO  [org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl] (default task-54) HHH000010: On release of batch it still contained JDBC statements
2018-10-17 20:12:47,572 ERROR [org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl] (default task-54) HHH000352: Unable to release batch statement...

      I’ve debugged where that is getting logged and all I can find is a single statement at the time.

      insert into EventLog (entityId, entityType, ipAddress, message, time, user, id) values (?, ?, ?, ?, ?, ?, ?)

      The only insert that is being created is actually being persisted to the database so this may be a spurious message.

      From my early debugging this appears to happen when 1 entity is persisted which does not need an immediate inset (due to having a generated pk) and then in another method of the same transaction an entity is persisted that does need an immediate insert because of a auto increment pk.

              smarlow1@redhat.com Scott Marlow
              cody.lerum@gmail.com Cody Lerum
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: