[
https://issues.apache.org/jira/browse/DERBY-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-5024:
---------------------------------
Description:
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.
was: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.
> 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, 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
