Hi all, I have an application that has a connection pool opened, to a certain database, with all connections having autocommit true; the default behaviour. Besides this, I keep a unique connection opened to the same database with autocommit false that I use to make changes in the configuration. The problem here happens when I try to use the connection with autocommit false, then I start getting exceptions like:
org.h2.jdbc.JdbcSQLException: Timeout trying to lock table "A_TABLE"; SQL statement: SELECT SOMETHING No matter how much I increase the LOCK_TIMEOUT I still get these exceptions. Using MVCC is not an option for me as this is a production database and the application became to behave very slow. What do you think is the problem here. Can't you keep at same time connections opened with autocommit = true and autocommit = false? Thanks, Dani. -- View this message in context: http://h2-database.66688.n3.nabble.com/mixed-connections-with-autocommit-true-and-false-tp4029781.html Sent from the H2 Database mailing list archive at Nabble.com. -- 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/d/optout.
