Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 7 Nov 2013 01:54:17 +0000 (UTC)
From: "Marty Backe (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12676750.1383185080430.31723.1383789257131@arcas>
In-Reply-To: <JIRA.12676750.1383185080430@arcas>
References: <JIRA.12676750.1383185080430@arcas>
Subject: [jira] [Comment Edited] (DERBY-6398) SYSCS_FREEZE_DATABASE locks-up
 if there are large records that haven't been flushed to the disk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815517#comment-13815517 ] 

Marty Backe edited comment on DERBY-6398 at 11/7/13 1:52 AM:
-------------------------------------------------------------

Auto-commit is not configured either way in our application. So I believe the default is, auto-commit = on

There is one connection object for the life of the application, so yes, the large update is performed using the same connection object as the freeze command.

The large update is an INSERT for a CLOB column

I will try and modify Derby as you suggest.


was (Author: martybacke):
Auto-commit is not configured either way in our application. So I believe the default is, auto-connect = on

There is one connection object for the life of the application, so yes, the large update is performed using the same connection object as the freeze command.

The large update is an INSERT for a CLOB column

I will try and modify Derby as you suggest.

> SYSCS_FREEZE_DATABASE locks-up if there are large records that haven't been flushed to the disk
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6398
>                 URL: https://issues.apache.org/jira/browse/DERBY-6398
>             Project: Derby
>          Issue Type: Bug
>          Components: Miscellaneous
>    Affects Versions: 10.10.1.1
>         Environment: Reliably demonstrated on Windows 7 with JDK 1.6.0_31
>            Reporter: Marty Backe
>             Fix For: 10.10.1.1
>
>         Attachments: report.txt
>
>
> 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.


--
This message was sent by Atlassian JIRA
(v6.1#6144)