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 "Kim Haase (JIRA)" <ji...@apache.org> on 2011/02/21 23:21:39 UTC

[jira] Updated: (DERBY-5024) Document the behavior of interrupt handling.

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

Kim Haase updated DERBY-5024:
-----------------------------

    Attachment: cdevdvlp22619.html
                DERBY-5024.diff

Attaching DERBY-5024.diff and cdevdvlp22619.html, with changes to the topic "Working with database threads in an embedded environment". I hope I've disentangled all the information about the new behavior without too many errors. Please let me know what changes are needed.


> 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, 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