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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2011/05/13 23:17:47 UTC
[jira] [Created] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
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.8.1.2, 10.7.1.1, 10.6.2.1, 10.6.1.0, 10.5.3.0, 10.5.2.0, 10.5.1.1, 10.4.2.0, 10.4.1.3, 10.3.3.0, 10.3.2.1, 10.3.1.4, 10.2.2.0, 10.2.1.6
Reporter: Dag H. Wanvik
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
[jira] [Commented] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041569#comment-13041569 ]
Knut Anders Hatlen commented on DERBY-5233:
-------------------------------------------
The patch looks fine to me. Two minor comments:
- The use of the success flag feels a little backwards. Perhaps it would be clearer if we only set it to true if the operation has succeeded?
- A comment in testInterruptShutdown() says "Assert and clear thread's flag:", but the code just below the comment doesn't clear the flag anymore. (It is cleared further down, so only the comment needs to be updated.)
> 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
[jira] [Updated] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-5233:
---------------------------------
Attachment: (was: Repro5233.java)
> 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
> Attachments: 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
[jira] [Commented] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041605#comment-13041605 ]
Dag H. Wanvik commented on DERBY-5233:
--------------------------------------
a) I agree it is awkward, I was following a preexisting pattern - I'll change both. b) Yes, I already corrected one of those, I apparently missed one, thanks.
> 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
[jira] [Updated] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-5233:
---------------------------------
Attachment: Repro5233.java
> 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
> Attachments: Repro5233.java, 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
[jira] [Updated] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-5233:
---------------------------------
Issue & fix info: [Patch Available, Repro attached] (was: [Repro attached])
Assignee: Dag H. Wanvik
> 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
[jira] [Resolved] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik resolved DERBY-5233.
----------------------------------
Resolution: Fixed
Fix Version/s: 10.9.0.0
10.8.1.3
Issue & fix info: [Repro attached] (was: [Repro attached, Patch Available])
> 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
> Fix For: 10.8.1.3, 10.9.0.0
>
> Attachments: DERBY-5233-1.diff, DERBY-5233-1.stat, DERBY-5233-2.diff, DERBY-5233-2.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
[jira] [Updated] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Mike Matrigali (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-5233:
----------------------------------
Component/s: Store
> 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
> Components: Store
> 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
> Fix For: 10.8.2.2, 10.9.0.0
>
> Attachments: DERBY-5233-1.diff, DERBY-5233-1.stat, DERBY-5233-2.diff, DERBY-5233-2.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-5233:
---------------------------------
Attachment: Repro5233.java
> 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
> Attachments: 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
[jira] [Updated] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-5233:
---------------------------------
Attachment: DERBY-5233-2.stat
DERBY-5233-2.diff
Uploading version #2.
> 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, DERBY-5233-2.diff, DERBY-5233-2.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
[jira] [Updated] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-5233:
---------------------------------
Attachment: DERBY-5233-1.stat
DERBY-5233-1.diff
Uploading a patch for this problem. I also adds a new test case to InterruptResilienceTest: testCreateDropInterrupted.
The patch makes RAFContainer, when seeing an interrupt exception during container creation, close it down and try again, up to MAX_INTERRUPT_RETRIES times. Since RAFContainer should work also under CDC/Foundation 1.1, the exceptions are checked using reflection (NIO classes are excluded there).
Running regressions.
> 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
> 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
[jira] [Commented] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041636#comment-13041636 ]
Dag H. Wanvik commented on DERBY-5233:
--------------------------------------
Committed as svn 1129764.
> 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, DERBY-5233-2.diff, DERBY-5233-2.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
[jira] [Commented] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041641#comment-13041641 ]
Dag H. Wanvik commented on DERBY-5233:
--------------------------------------
Backported to 10.8 branch as svn 1129769, resolving.
> 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
> Fix For: 10.8.1.3, 10.9.0.0
>
> Attachments: DERBY-5233-1.diff, DERBY-5233-1.stat, DERBY-5233-2.diff, DERBY-5233-2.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
[jira] [Commented] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (DERBY-5233) Interrupt of create table or index
(i.e. a container) will throw XSDF1 under NIO - connection survives
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-5233:
---------------------------------
Bug behavior facts: [Seen in production]
Setting "seen in production" flag, cf. duplicated issue DERBY-5237 posted by a user.
> 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
> Attachments: 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