Project

General

Profile

Bug #125

Configured transaction timeout is overridden with hard-coded value

Added by Alex Hall - over 14 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Mulgara
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
fixed

Description

The transaction timeout for use with database transactions is configurable in the Mulgara config file. However, the configured transaction timeout is overridden with a hard-coded value of one hour in the DatabaseSession constructor (DatabaseSession.java, line 238-239) :

<pre>

The hard-coded value of one hour is not long enough for loading very large files.
#1

Updated by ronald - over 14 years ago

Fixed in r977.

To be closed when source:branches/mgr-121-lockrecovery is merged into trunk.

#2

Updated by ronald - over 14 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Branch merged in r1098.

Also available in: Atom PDF