aarrrrgghhhh.... it keeps happening!!!
I have used the most recent version (1.0.63) but the following
exception keep filling the log file:
Caused by: org.h2.jdbc.JdbcBatchUpdateException: Timeout trying to
lock table CONTENTASSETRESPONSE [HYT00-50]
at
org.h2.jdbc.JdbcPreparedStatement.executeBatch(JdbcPreparedStatement.java:1040)
at
org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
at
org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:242)
... 36 more
I don't encounter the exception if I do things very slow (one by one),
but once I stress test my app (using JMeter, 1000hits), it throws the
exception. using MySQL everything is OK (I only changed driver and
DB-connection configuration).
anyway, Merry Christmas :-)
On Dec 26, 2007 11:43 PM, Thomas Mueller <thom...@gmail.com> wrote:
Hi,
I don't think so. Did you get my first response? Here again:
According to the exception code (-50) you are using version 1.0.50 from
2007-06-17. You should consider using a newer version. In newer versions,
read committed is the default isolation level (like in most other
databases). With older versions (including the version you are using), the
default isolation level is serializable, where such scenarios can easily
lead to lock timeout.
9 messages in com.googlegroups.h2-databaseRe: Timeout trying to lock... [HYT00-50]
