Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 14 Feb 2011 18:49:57 +0000 (UTC)
From: "Mike Matrigali (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1520054190.15409.1297709397557.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (DERBY-4741) Make embedded Derby work reliably in
 the presence of thread interrupts
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 ]

Mike Matrigali updated DERBY-4741:
----------------------------------

    Urgency: Normal
     Labels: derby_triage10_8  (was: )

triaged for 10.8.

A lot of progress has been made on this issue, and it looks ready for 10.8.=
  Work is being done incrementally, probably soon should close this one bas=
ed on checked in work, and log a new one to track possible work post 10.8.

> Make embedded 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
>              Labels: derby_triage10_8
>         Attachments: InterruptResilienceTest.java, MicroAPITest.java, der=
by-4741-a-01-api-interruptstatus.diff, derby-4741-a-01-api-interruptstatus.=
stat, derby-4741-a-02-api-interruptstatus.diff, derby-4741-a-02-api-interru=
ptstatus.stat, derby-4741-a-03-api-interruptstatus.diff, derby-4741-a-03-ap=
i-interruptstatus.stat, derby-4741-a-04-api-interruptstatus.diff, derby-474=
1-a-04-api-interruptstatus.stat, derby-4741-all+lenient+resurrect.diff, der=
by-4741-all+lenient+resurrect.stat, derby-4741-b-01-nio.diff, derby-4741-b-=
01-nio.stat, derby-4741-b-02-nio.diff, derby-4741-b-02-nio.stat, derby-4741=
-b-03-nio.diff, derby-4741-b-03-nio.stat, derby-4741-b-04-nio.diff, derby-4=
741-b-04-nio.stat, derby-4741-c-01-nio.diff, derby-4741-c-01-nio.stat, derb=
y-4741-kristians-01.diff, derby-4741-nio-container+log+waits+locks+throws.d=
iff, derby-4741-nio-container+log+waits+locks+throws.stat, derby-4741-nio-c=
ontainer+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-contai=
ner+log+waits+locks.stat, derby-4741-nio-container+log+waits.diff, derby-47=
41-nio-container+log+waits.stat, derby-4741-nio-container+log.diff, derby-4=
741-nio-container+log.stat, derby-4741-nio-container-2.diff, derby-4741-nio=
-container-2.log, derby-4741-nio-container-2.stat, derby-4741-nio-container=
-2b.diff, derby-4741-nio-container-2b.stat, derby-4741-raf-stresstest-1.dif=
f, derby-4741-raf-stresstest-1.stat, derby-4741-raf-stresstest-2.diff, derb=
y-4741-raf-stresstest-2.stat, derby-4741-raf-stresstest-3.diff, derby-4741-=
raf-stresstest-3.stat, derby-4741-raf-stresstest-4.diff, derby-4741-raf-str=
esstest-4.stat, derby-4741-sleeps-waits-1.diff, derby-4741-sleeps-waits-1.s=
tat, derby-4741-sleeps-waits-2.diff, derby-4741-sleeps-waits-2.stat, derby-=
4741-sleeps-waits-3.diff, derby-4741-sleeps-waits-3.stat, derby-4741-testBa=
tchInterrupt-b.diff, derby-4741-testBatchInterrupt.diff, derby-4741-testQue=
ryInterrupt.diff, derby-4741-testQueryInterrupt.stat, derby.log, derby.log,=
 interrupts-fs.html, interrupts-fs.html, interrupts-fs.html, 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 for extra concurrency.
> If a 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 store can be left in an inconsiste=
nt state, although no data is corrupted, and we therefore have to return a =
database level error to perform shutdown and recovery. This means the appli=
cations can no longer access the database while a shutdown and reboot inclu=
ding a recovery is taking place.
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira