You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2011/03/01 04:01:39 UTC
[jira] Commented: (DERBY-5024) Document the behavior of interrupt
handling.
[ https://issues.apache.org/jira/browse/DERBY-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000675#comment-13000675 ]
Dag H. Wanvik commented on DERBY-5024:
--------------------------------------
Thanks, Kim! The exception here is when one actually *intends* to kill the connection by an interrupt, presumably because it is taking too long.
I *think* pre-existing wording here refers to a practice of releasing waiting threads waiting on an arbitrary monitor (threads which are also sometimes doing embedded Derby calls), by interrupting them instead of Object#notify. When a thread calls Object#wait, it can be released from that wait by a Object#notify *or* an interrupt. I think the existing wording in our docs warns against that practice for threads that also field Derby calls. If others have different interpretations if this, please speak up :) Cf also Javadoc http://download.oracle.com/javase/6/docs/api/java/lang/Object.html#wait().
Presumably, the thread releasing the resource doesn't know for sure what the other (possibly waiting threads are doing).. Notify or NotifyAll is the correct idiom as a rule :)
> 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
> Attachments: DERBY-5024-2.diff, DERBY-5024.diff, DERBY-5042-2.diff, cdevdvlp22619.html, cdevdvlp22619.html
>
>
> DERBY-4741 improves Derby's handling of interrupts. Now the engine
> does not fall over when an interrupt occurs. Instead, Derby only kills
> the connection which is running when the interrupt happens, which may
> also be useful to stop execution in certain situations. Other times
> the connection will survive, i.e. the interrupt is ignored by Derby,
> although the interrupt status flag is kept. 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