Hi,
I'm sorry, but I'm not familiar with JBoss. I know that the 2-phase-commit
implementation of H2 is currently incomplete, and probably this is the root
cause of the problem.
What H2 can't do currently is: after a crash, in the recovery phase, H2
doesn't allow to start a new transaction until all in-doubt transactions
are either rolled back or committed.
I hope I can implement this missing features in the future, but demand for
this feature is relatively low so far. Unfortunately with the current
storage it's not possible to implement it (at least not easily); it will
have to wait until the MVStore storage is ready.
Note: having recovery is also not 'a must' for me actually, so would there
> be a way to proceed from this situation, somehow skipping recovery?
>
Well, you could roll back all in-doubt transactions. This would be a manual
step however:
SELECT * FROM INFORMATION_SCHEMA.IN_DOUBT ;
and then for each transaction, run:
ROLLBACK TRANSACTION <name>
(or COMMIT TRANSACTION <name>). Then re-open the database (close all
connections or run "shutdown").
Regards,
Thomas
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
