,
Thomas
On Thu, Dec 18, 2014 at 1:53 PM, Dieter Cailliau dieter@gmail.com
wrote:
File corrupted while reading record: /tmp/bms.auto.mv.db. Possible
solution: use the recovery tool [90030-182]
http://127.0.1.1:8082/login.do?jsessionid=cd6441ab484bba9d2abe4db0d5455f69#
90030/90030
.
Regards,
Thomas
On Thu, Dec 18, 2014 at 1:53 PM, Dieter Cailliau dieter@gmail.com
javascript: wrote:
File corrupted while reading record: /tmp/bms.auto.mv.db. Possible
solution: use the recovery tool [90030-182]
http://127.0.1.1:8082/login.do?jsessionid
The fix is in Version 1.3.174 (2013-10-19).
Is it possible to find out in which version the bug was introduced? I have
deployments using 1.3.168 and i don't remember having seen this happening.
I have seen it happening in 1.3.173 though. I'm wondering whether to
upgrade the 1.3.168
) the database itself creates
temporary tables.
If you still have the database file, could you send it to me please? I
would like to analyze it.
Regards,
Thomas
On Tuesday, March 18, 2014, Dieter Cailliau
dieter@gmail.comjavascript:
wrote:
URL: jdbc:h2:/tmp/bms;DB_CLOSE_DELAY=-1
URL: jdbc:h2:/tmp/bms;DB_CLOSE_DELAY=-1;LOCK_TIMEOUT=5000
According to your query, the create_build was 168.
I'm not using temporary tables (afaik) just regular JPA (hibernate inside
jboss7).
I didn't see OutOfMemory in my logs, but they don't go back to the first
occurence of the problem, so
With 1.3.175 the error message is a bit longer:
Uniqhttp://127.0.1.1:8082/test.do?jsessionid=4ea64ad64b043f1dd5de67ef7339a197#ue
index or primary key violation: SYS_ID ON PUBLIC.SYS(ID) VALUES ( /*
key:266 */ 15, 0, 3, 'CREATE SEQUENCE
Thanks! That works fine.
--
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 h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to
Yes I'm using 2-phase-commit because I use xa-datasource (this is an xml
element in jboss' standalone-full-ha.xml), but I never really found out how
to configure the thing (jboss as 7.2.0.Final with h2) to perform recovery.
I've pasted the config xml below.
Note: having recovery is also not 'a
On Tue, Oct 1, 2013 at 4:12 PM, Dieter Cailliau
dieter@gmail.comjavascript:
wrote:
I assume that that fact (that the h2 version with which i created the
schema = 1.3.161) is not relevant for the problem experienced in 1.3.168
which is still a problem in 1.3.168?
It is true that i have
On Tuesday, August 13, 2013, Dieter Cailliau wrote:
jdbc:h2:/tmp/x;DB_CLOSE_DELAY=-1;LOCK_TIMEOUT=5000
It's a small db (3M on a windows7) with small tables (about 100 rows).
I'm using multiple threads.
I attached the empty schema. If it helps i can send you a (non-corrupt)
populated one. I'm still
I'm using h2-1.3.168 in jboss 7.2.0.Final on a Win7.
--
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 h2-database+unsubscr...@googlegroups.com.
To post to this
Every insert gives this in bms.trace.db
org.h2.jdbc.JdbcSQLException: The database is read only; SQL statement:
insert into Element (lastSeen, sources, name, options, tupple, host_string,
assets2, DTYPE, string) values (?, ?, ?, ?, ?, ?, ?,
'DeviceCapabilityService', ?) [90097-168]^M
at
Here's another example of ArrayIndexOutOfBoundsException at
org.h2.index.PageDataLeaf.getRowAt: this happened on 1.3.168. The most
recent fix i found in changelog about this kind of error was 1.3.166, so
probably there's still something wrong since then, or have there been fixes
related to
13 matches
Mail list logo
