We are looking at adopting this latest version of H2 and take advantage of
MVCC. If I start our application using the URL,
"jdbc:h2:mem:/tmp/guidewire/ferrite/pxjajp", it starts fine. If I start it
with "jdbc:h2:file:/tmp/guidewire/ferrite/pxjajp", however, it fails with
an NPE at
Caused by:
Mvcc is still a little flakey so I suspect you have a corrupt database
there.
On Friday, 7 March 2014, Wes Clark wrote:
> We don't normally specify "user" or "password" when we get a connection.
> That has always worked. I don't know if that is involved.
>
> --
> You received this message beca
Hi,
Looking at the stack trace, the problem could also be related to using a
old version of H2 together with a database created by a newer version. To
find out what version of H2 you are using, could you post the complete
stack trace including error message and error codes?
Regards,
Thomas
On
If I drop the database and start the test, the database is created and
seems to run okay. If I start the test again, it immediately fails with
the stack trace shown in my first message. Now, during the first
"successful" run, I am getting the NPE error documented in another thread
when I prep
If I drop the database and start the test, the database is created and
seems to run okay. If I start the test again, it immediately fails with
the stack trace shown in my first message. Now, during the first
"successful" run, I am getting the NPE error documented in another thread
when I prep
Okay: If I start our application on an empty database, the h2_file
database gets created and the application starts fine. If I shut down the
application and start it again, I immediate get
Caused by: java.lang.NullPointerException
at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:9
The JDBC URL being used is
jdbc:h2:file:/tmp/guidewire/emerald/px;MVCC=TRUE
On Thursday, March 13, 2014 3:14:34 PM UTC-7, Wes Clark wrote:
>
> Okay: If I start our application on an empty database, the h2_file
> database gets created and the application starts fine. If I shut down the
> appli
Hi,
To find out what version of H2 you are using, could you post the complete
stack trace including error message and error codes?
Regards,
Thomas
On Thu, Mar 13, 2014 at 11:15 PM, Wes Clark wrote:
> The JDBC URL being used is
>
> jdbc:h2:file:/tmp/guidewire/emerald/px;MVCC=TRUE
>
>
> On Thu
With 1.3.174, this problem disappears, and I don't need any functionality
in 1.3.175, so I consider this closed.
On Friday, March 14, 2014 1:00:03 AM UTC-7, Thomas Mueller wrote:
>
> Hi,
>
> To find out what version of H2 you are using, could you post the complete
> stack trace including error m
