[DERBY-6398] SYSCS_FREEZE_DATABASE locks-up if there are large records that haven't been flushed to the disk

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.10.1.1
• Fix Version/s: 10.10.1.1
• Component/s: Store
• Environment: Reliably demonstrated on Windows 7 with JDK 1.6.0_31
• Urgency: Normal
• Issue & fix info: Repro attached
• Bug behavior facts: Seen in production
• Assignee: Unassigned
• Reporter: Marty Backe
• Created: 31/Oct/13 02:04
• Updated: 07/Nov/13 09:48

Description

If after writing a record that contains a large data column (>100KB), the FREEZE command is issued, the command never returns (Derby appears to be dead-locked).

E.g. sqlStatement.executeUpdate("CALL SYSCS_UTIL.SYSCS_FREEZE_DATABASE()");

If the CALL SYSCS_UTIL.SYSCS_CHECKPOINT_DATABASE() command is first used before calling FREEZE, it does not lock-up.

It's my opinion that calling FREEZE should never result in a dead-locked Derby instance.

Issue Links

• relates to: DERBY-5632 Logical deadlock happened when freezing/unfreezing the database