[jboss-jira] [JBoss JIRA] (WFLY-11213) On release of batch it still contained JDBC statements logged

[Cody Lerum (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650118#comment-13650118 ] 

Cody Lerum commented on WFLY-11213:
-----------------------------------

[~guillaume.smet] I did create a test case https://github.com/codylerum/hibernate-test-case-templates/tree/batch_statements but I was unable to get the log message to fire.

I suspected it has something to do with the integration of the JTA Tx or something. Maybe someone who knows more about hibernate test cases can look at the demo project and the test case and modify it to trigger.

> On release of batch it still contained JDBC statements logged
> -------------------------------------------------------------
>
>                 Key: WFLY-11213
>                 URL: https://issues.jboss.org/browse/WFLY-11213
>             Project: WildFly
>          Issue Type: Bug
>          Components: JPA / Hibernate
>    Affects Versions: 14.0.1.Final
>         Environment: Java 8_181
> Wildfly 14.0.1.Final
>            Reporter: Cody Lerum
>            Assignee: Scott Marlow
>            Priority: Major
>
> 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
> {code:java}
> 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...
> {code}
> 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.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)