[DERBY-5233] Interrupt of create table or index (i.e. a container) will throw XSDF1 under NIO - connection survives

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 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
• Fix Version/s: 10.8.2.2, 10.9.1.0
• Component/s: Store
• Issue & fix info: Repro attached
• Bug behavior facts: Seen in production
• Assignee: Dag H. Wanvik
• Reporter: Dag H. Wanvik
• Created: 13/May/11 21:15
• Updated: 17/Jun/13 09:19
• Resolved: 31/May/11 16:04

Description

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.

Issue Links

• is duplicated by: DERBY-5237 interrupting thread performing "create table" doesn't cause SQLException with sql state "08000"
• is part of: DERBY-4741 Make embedded Derby work reliably in the presence of thread interrupts