[
https://issues.apache.org/jira/browse/DERBY-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-5024:
-----------------------------
Attachment: DERBY-5042-2.diff
cdevdvlp22619.html
Thanks, Dag! I'm attaching DERBY-5042-2.diff and cdevdvlp22619.html, which I
hope make the changes you asked for. I made a few language changes.
There is one question in my mind about this first change:
"Do not normally use Thread#interrupt to signal possibly waiting threads ..."
When, instead of a blanket prohibition, we say you shouldn't *normally* do
something, it raises the question, under what circumstances *would* you do it?
I don't think we answer that question. Should we?
(BTW, I changed "normally" to "As a rule" and put it at the beginning -- more
common usage.)
> 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.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
