Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <16377051.111731288236919764.JavaMail.jira@thor>
Date: Wed, 27 Oct 2010 23:35:19 -0400 (EDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4741) Make Derby work reliably in the
 presence of thread interrupts
In-Reply-To: <13345993.330341278959929752.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-4741?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik updated DERBY-4741:
---------------------------------

    Attachment: derby-4741-a-03-api-interruptstatus.stat
                derby-4741-a-03-api-interruptstatus.diff

Uploading version a-03, minor and clerical changes only relative to a-02.

> 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: Bug
>          Components: Store
>    Affects Versions: 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10=
.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>         Attachments: derby-4741-a-01-api-interruptstatus.diff, derby-4741=
-a-01-api-interruptstatus.stat, derby-4741-a-02-api-interruptstatus.diff, d=
erby-4741-a-02-api-interruptstatus.stat, derby-4741-a-03-api-interruptstatu=
s.diff, derby-4741-a-03-api-interruptstatus.stat, derby-4741-all+lenient+re=
surrect.diff, derby-4741-all+lenient+resurrect.stat, derby-4741-nio-contain=
er+log+waits+locks+throws.diff, derby-4741-nio-container+log+waits+locks+th=
rows.stat, derby-4741-nio-container+log+waits+locks-2.diff, derby-4741-nio-=
container+log+waits+locks-2.stat, derby-4741-nio-container+log+waits+locks.=
diff, derby-4741-nio-container+log+waits+locks.stat, derby-4741-nio-contain=
er+log+waits.diff, derby-4741-nio-container+log+waits.stat, derby-4741-nio-=
container+log.diff, derby-4741-nio-container+log.stat, derby-4741-nio-conta=
iner-2.diff, derby-4741-nio-container-2.log, derby-4741-nio-container-2.sta=
t, derby-4741-nio-container-2b.diff, derby-4741-nio-container-2b.stat, derb=
y.log, derby.log, MicroAPITest.java, xsbt0.log.gz
>
>
> When not executing on a small device VM, Derby has been using the Java NI=
O classes java.nio.clannel.* for file io.
> If thread is interrupted while executing blocking IO operations in NIO, t=
he ClosedByInterruptException will get thrown. Unfortunately, Derby isn't c=
urrent 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 app=
lications can no longer access the database without a shutdown and reboot i=
ncluding a recovery.
> It would be nice if Derby could somehow detect and finish IO operations u=
nderway when thread interrupts happen before passing the exception on to th=
e application. Derby embedded is sometimes embedded in applications that us=
e Thread.interrupt to stop threads.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.