db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2291) Add timeout on latch wait
Date Mon, 05 Feb 2007 15:13:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470244

Bryan Pendleton commented on DERBY-2291:

I'm not sure I totally agree. I think you could argue that just staying hung is better, in
the hopes that eventually somebody will come along and grab a stack trace or attach a debugger
or something like that, and then the dead lock will be directly apparent from the stack traces
of the various threads. If you time out and break the deadlock, the information about the
various thread stacks will be lost.

> Add timeout on latch wait
> -------------------------
>                 Key: DERBY-2291
>                 URL: https://issues.apache.org/jira/browse/DERBY-2291
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
> If a bug causes a dead lock in the latching, Derby may hang infinitely. A timeout could
make it easier to detect the cause of the hang.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message