db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-5024) Document the behavior of interrupt handling.
Date Tue, 01 Mar 2011 18:10:36 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kim Haase resolved DERBY-5024.

          Resolution: Fixed
       Fix Version/s:
    Issue & fix info:   (was: [Patch Available])

Thanks, Dag, for that information! I expect most readers will know more about threads than
I do, so I have committed the patch you approved as is.

Committed patch DERBY-5024-2.diff to documentation trunk at revision 1075954. 

> 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:
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>             Fix For:
>         Attachments: DERBY-5024-2.diff, DERBY-5024.diff, DERBY-5042-2.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


View raw message