Message Title

Steve Ebersole commented on an issue

Michael Wyraz Even though the logs show "On release of batch it still contained JDBC statements", look at where/how that is used in the new code. It is used in a code block cleaning up the statements. Its just a warning to you that this is happening.

Really I just need a test case showing this happening, ideally in a supported means. Spring is breaking the explicit contract of Session here based on your explanation. If I can support them in doing how they try to do it, I will. But that means getting me a test case showing this behavior sans any Spring stuff; just a plain Hibernate usage

Add Comment

Hibernate ORM /

HHH-7688

In NonBatchingBatch.addToBatch() are some bugs (missing try...finally) that leaves the class in an undefined condition if the statement there fails. In addition, statements are not closed on error.

I have attached a project that shows the bug and contains a fix.

Here's my complete description (which you will also find in ShowBug.java):

/**
...

This message was sent by Atlassian JIRA