Oystein Grovlen wrote:
This means that the thread accessing the database have been
interrupted. Do you have code that may interrupt running threads?
In this particular case it happened while the thread was flushing log
to disk during commit. From the log it seems that the db is not able
to recover from this; it is not able to rollback the transaction, and
the database is shutdown since it will be left in an inconsistent state.
I think this indicates a bug in Derby. For robustness, it needs to
handle that threads are interrupted.
Is this the same as DERBY-151?
Kathey
