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] Commented: (DERBY-5024) Document the behavior of interrupt handling.
Date Thu, 17 Feb 2011 21:07:12 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996076#comment-12996076
] 

Kim Haase commented on DERBY-5024:
----------------------------------

Thanks, Rick -- that helps, since DERBY-4741 is a large and daunting JIRA. 

One question for starters:

"If a Thread is interrupted and the flag is not cleared" ...

What flag is that? Is this the "interrupted status" that is tested by interrupted() and isInterrupted()
but is otherwise not accessible programmatically?

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

        

Mime
View raw message