search

lbehnke / h2database

Automatically exported from code.google.com/p/h2database
0 stars 0 forks source link

MVCC with connection pooling in tomcat #105

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I wanted to upgrade the database from version 1.1.112 to 1.1.116. With 112
it works to create a connection pool for an embedded database. With 116 it
says that it is not possible to set the MVCC parameter on an open database. 

What steps will reproduce the problem?
(simple SQL scripts or simple standalone applications are preferred)

1. Install Tomcat and add a connection pool for H2 with version 1.1.116
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system, file
system, and virtual machine?

Windows 32 Bit, Sun JVM 1.6 update 14.

Do you know a workaround?

Stay with version 1.1.112 :-(

How important/urgent is the problem for you?

In your view, is this a defect or a feature request?

defect ?

Please provide any additional information below.

Original issue reported on code.google.com by mborcher...@gmail.com on 30 Jul 2009 at 12:04

GoogleCodeExporter commented 9 years ago 
Hi,

Sorry I can not reproduce this problem. Could you post a simple, standalone 
test case
that reproduces the problem? It would be great if the test case does not have 
any
dependencies except the H2 jar file (that is, a simple SQL script that can be 
run in
the H2 Console, or a Java class uses the JDBC API and is run using a static main
method). Please include any initialization code (CREATE TABLE, INSERT and so 
on) in
the Java class or in a .sql script file.

Regards,
Thomas

Original comment by thomas.t...@gmail.com on 2 Aug 2009 at 4:28

GoogleCodeExporter commented 9 years ago 
This happens if MVCC=1:

org.h2.jdbc.JdbcSQLException: Cannot change the setting MVCC when the database 
is 
already open; SQL statement: SET MVCC 1 [90133-114]

Error does not happen if MVCC=TRUE

Original comment by a.kosenkov on 12 Aug 2009 at 1:32

GoogleCodeExporter commented 9 years ago 
OK, I will support MVCC=1 in the next release. However, this is not how it is
documented. I will close the bug now, if it is not solved please add a 
reproducible
test case and then I will re-open the bug.

Original comment by thomas.t...@gmail.com on 15 Aug 2009 at 7:19