Closed GoogleCodeExporter closed 9 years ago
Most likely the problem is the database URL:
jdbc:h2:tcp://172.24.168.41/bpelseDB;MODE=Derby
Try using an absolute path such as:
jdbc:h2:tcp://172.24.168.41/file:/data/bpelseDB;MODE=Derby
or
jdbc:h2:tcp://172.24.168.41/~/data/bpelseDB;MODE=Derby
See also
http://www.h2database.com/html/features.html#embedded_databases
Original comment by thomas.t...@gmail.com
on 22 Apr 2009 at 8:46
Thanks. I had to give file: path.
Original comment by rohit.c.joshi@gmail.com
on 22 Apr 2009 at 9:45
OpenESB/BPLE-SE is able to connect to H2 database. When it updates the
timestamp, I
get following error. It seems TIMESTAMPDIFF function is not supported.
NOTE:I am connecting using MODE=Derby.
[#|2009-04-22T17:40:12.883-0400|WARNING|sun-appserver2.1|com.sun.jbi.engine.bpel
.BPELSEInOutThread|_ThreadID=15;_ThreadName=sun-bpel-engine-thread-0;_RequestID=
7a02f1d8-35b1-4333-8cc1-d76f207125de;|BPJBI-6004:
caught exception while processing message
java.lang.RuntimeException: org.h2.jdbc.JdbcSQLException: Function
TIMESTAMPDIFF not
found; SQL statement:
update STATE set engineid = ? where (status = 'RUNNING' or status =
'SUSPENDED')
and engineid IN (select engineid from ENGINE where
TIMESTAMPDIFF(SQL_TSI_SECOND,
timestamp(lastupdatetime), CURRENT_TIMESTAMP) > ? / 1000 and engineid != ?)
[90022-111]
at org.h2.message.Message.getSQLException(Message.java:107)
at org.h2.message.Message.getSQLException(Message.java:118)
at org.h2.message.Message.getSQLException(Message.java:77)
Any workaround to support TIMESTAMPDIFF would be appreciated.
Original comment by rohit.c.joshi@gmail.com
on 22 Apr 2009 at 9:49
I have written a TIMESTAMPDIFF function and seem to be working fine. Now it
complains about timestamp() function.
Original comment by rohit.c.joshi@gmail.com
on 22 Apr 2009 at 10:51
Giving up on H2 and going to try HSQLDB (:
Original comment by rohit.c.joshi@gmail.com
on 23 Apr 2009 at 1:15
timestamp() is not supported, use CAST(... AS TIMESTAMP) instead.
Original comment by thomas.t...@gmail.com
on 27 Apr 2009 at 6:27
Original issue reported on code.google.com by
rohit.c.joshi@gmail.com
on 22 Apr 2009 at 8:31Attachments: