Make Derby work reliably in the presence of thread interrupts
-------------------------------------------------------------
Key: DERBY-4741
URL: https://issues.apache.org/jira/browse/DERBY-4741
Project: Derby
Issue Type: Improvement
Components: Store
Affects Versions: 10.6.1.0, 10.5.3.0, 10.5.2.0, 10.5.1.1, 10.4.2.0,
10.4.1.3, 10.3.3.0, 10.3.2.1, 10.3.1.4, 10.2.2.0, 10.2.1.6
Reporter: Dag H. Wanvik
When not executing on a small device VM, Derby has been using the Java NIO
classes java.nio.clannel.* for file io.
If thread is interrupted while executing blocking IO operations in NIO, the
ClosedByInterruptException will get thrown. Unfortunately, Derby isn't current
architected to retry and complete such operations (before passing on the
interrupt), so the Derby database can be left in an inconsistent state and we
therefore have to return a database level error. This means the applications
can no longer access the database without a shutdown and reboot including a
recovery.
It would be nice if Derby could somehow detect and finish IO operations
underway when thread interrupts happen before passing the exception on to the
application. Derby embedded is sometimes embedded in applications that use
Thread.interrupt to stop threads.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
