[
https://issues.apache.org/jira/browse/DERBY-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996031#comment-12996031
]
Kim Haase commented on DERBY-5024:
----------------------------------
I've read the functional spec for DERBY-4741, but I'm still a bit confused
about what has changed from the user's point of view.
I'm guessing the topic "Working with database threads in an embedded
environment" needs to be changed
(http://db.apache.org/derby/docs/dev/devguide/devguide-single.html#cdevdvlp22619),
but I'm not sure exactly how.
Can you now use interrupt, as well as wait and notify, to notify threads that
are accessing a database in an embedded environment? With the proviso that on
Solaris you cannot do this on JDK 1.4, and on JDK 5 and 6 you can do it only if
you run java with the option "-XX:-UseVMInterruptibleIO"?
Will an interrupt close the database connection [but not cause Derby to shut
down] if this can be done safely, but will otherwise be ignored?
Thanks for any guidance.
> Document the behavior of interrupt handling.
> --------------------------------------------
>
> Key: DERBY-5024
> URL: https://issues.apache.org/jira/browse/DERBY-5024
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.8.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
>
> DERBY-4741 improves Derby's handling of interrupts. Now the engine does not
> fall over when an interrupt occurs. Instead, at worst, Derby only kills the
> Connection which is running when the interrupt happens. And sometimes that
> Connection will survive too so that the interrupt is silently swallowed. The
> exact behavior has been discussed on DERBY-4741 from 2011-02-10 onward.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
