Hi, > with the exception that they do not log exceptions
Yes. Creating exceptions is very slow in Java (filling the stack trace is the slow part). Of course, logging exceptions is probably even slower, but if possible both should be avoided. For H2, logging exceptions can be disabled by appending ";TRACE_LEVEL_FILE=0" to the database URL. But it would make sense to not create exceptions at all; I wonder if this is really a Hibernate bug. Regards, Thomas On Mon, Feb 10, 2014 at 9:59 AM, Axel Röber <[email protected]> wrote: > 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. > -- 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.
