[
https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041614#comment-13041614
]
Dag H. Wanvik commented on DERBY-5233:
--------------------------------------
Thanks for looking at the patch, Knut! Re a) Actually, I think it gets less
clear if I change it around: the normal case is that we'll not loop, indicated
by the early setting of the success flag. Only exceptionally will we loop using
a continue, so I think I prefer setting success = false there. I'd rather
burden the abnormal case with extra logic than the normal case.
> Interrupt of create table or index (i.e. a container) will throw XSDF1 under
> NIO - connection survives
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5233
> URL: https://issues.apache.org/jira/browse/DERBY-5233
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0,
> 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0, 10.6.2.1,
> 10.7.1.1, 10.8.1.2
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Attachments: DERBY-5233-1.diff, DERBY-5233-1.stat, Repro5233.java
>
>
> Cf the enclosed repro. It would be good to make Derby ignore the interrupt
> here. Cf DERBY-4741. Note that this is less serious than in the cases
> referred to in DERBY-4741: here the database does not get shut down, even the
> connection survives, cf the repro. So, this can be considered a follow-up to
> DERBY-4741 to further improve Derby's robustness under interrupts.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
