I partly agree that this is a bug in hibernate. But Derby and HSQLDB are working also fine (as H2) in this scenario - with the exception that they do not log exceptions. I guess they only don't check the closure state of the object. But as the application itself works fine, it seems that the H2 exceptions in the trace file are a kind of warning. And I am looking for a way to disabe this. And it is interesting whether someone else has made some experience with H2 and Hibernate 4.3(.1).
> That looks like a bug in Hibernate - it should not be calling that method > on a closed Statement object. > I suggest you bring it up on the Hibernate mailing list. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
