Closed GoogleCodeExporter closed 9 years ago
This issue happened yet again on the same database and bouncing the JVM again
seemed to have fixed the issue.
I tried looking at what could have caused this issue, but have still not found
a root cause yet. I do not know how to reproduce this either. Will keep you
posted on the same.
In the meanwhile, would it be possible to shed any light as to why this could
be happening?
Thanks.
Original comment by itspa...@gmail.com
on 31 Mar 2011 at 5:00
Hi,
Sorry for the delay!
You are using quite an old version. Is the problem reproducible with a more
recent version, for example version 1.3.153?
Do you use triggers?
Regards,
Thomas
Original comment by thomas.t...@gmail.com
on 4 Apr 2011 at 5:39
Hello,
This is an older version because we use it in our product that we ship to
customers. And its weird, in my 2.5 years experience of using H2, this is the
first time I am seeing this. I do not know the internals of H2 well enough to
even guess what could be the cause (or the exact issue).
So, I will try and see if this issue occurs in the version you mention. But, do
you know what is this a symptom of? Like I said, this is just a temporary
situation because when we bounce our server, the issue seems to have gone away.
And we do not use triggers.
Thanks,
Pavan
Original comment by itspa...@gmail.com
on 5 Apr 2011 at 4:21
> do you know what is this a symptom of?
I'm not sure exactly, but it looks similar to a problem that was solved some
time ago, where a deleted row was deleted again within a trigger. I guess it
could also happen if you update or delete the row within a Java function, but
I'm not sure.
If the problem still occurs, I would be very interested in trying to solve it.
Original comment by thomas.t...@gmail.com
on 5 Apr 2011 at 5:45
Hey,
So, we do not have any triggers on the DB.
We run a *lot* of queries and our server is highly transactional. All the
transactions, however, perform only updates i.e. we do not have any delete
statements that get executed on any of the tables.
Also, this exception was happening on all select statements that were being
executed as well and during updating.
Since this is happening on a client setup, its hard to get all the things that
would help me reproduce this issue. I currently have their .h2.db file. Will
try and see what can be done to reproduce this issue.
- Pavan
Original comment by itspa...@gmail.com
on 5 Apr 2011 at 7:11
I'm closing the issue as 'works for me' currently. I will re-open it once we
have more info.
Original comment by thomas.t...@gmail.com
on 11 Sep 2011 at 3:03
Original issue reported on code.google.com by
itspa...@gmail.com
on 29 Mar 2011 at 5:00