litedb-org/LiteDB · warning · TimeoutException

Timed out waiting for ReleaseTransaction to finish.

Error message

Timed out waiting for ReleaseTransaction to finish.

What it means

Thrown by the Issue 2561 repro harness when a background worker thread does not signal completion within a 10-second window. The worker reflects into the LiteEngine's TransactionMonitor and calls ReleaseTransaction on a captured transaction; if that reflection path deadlocks or hangs, reproObserved.Wait returns false. It is a test-harness timeout, not a normal LiteDB runtime error.

Source

Thrown at LiteDB.ReproRunner/Repros/Issue_2561_TransactionMonitor/Program.cs:137

                observedException = liteException;
                Log(host, "Observed LiteException from ReleaseTransaction on worker thread:");
                Log(host, liteException.ToString());
            }
            finally
            {
                reproObserved.Set();
            }
        })
        {
            IsBackground = true,
            Name = "Issue2561-Repro-Worker"
        };

        worker.Start();

        if (!reproObserved.Wait(TimeSpan.FromSeconds(10)))
        {
            throw new TimeoutException("Timed out waiting for ReleaseTransaction to finish.");
        }

        rollback.Invoke(engine, Array.Empty<object>());

        if (observedException is null)
        {
            throw new InvalidOperationException("Expected LiteException was not observed.");
        }

        if (!observedException.Message.Contains("current thread must contains transaction parameter", StringComparison.OrdinalIgnoreCase))
        {
            throw new InvalidOperationException($"LiteException did not contain expected message. Actual: {observedException.Message}");
        }

        Log(host, "Repro succeeded: ReleaseTransaction threw on the wrong thread.");
    }

    private static void Log(ReproHostClient host, string message, ReproHostLogLevel level = ReproHostLogLevel.Information)

View on GitHub (pinned to f906a5f850)

Solutions

1. Increase the timeout passed to reproObserved.Wait if running under a debugger or slow CI.
2. Confirm the LiteDB build under test still throws LiteException from ReleaseTransaction on the wrong thread; if the fix removed that path the repro is obsolete.
3. Run the repro outside of an attached debugger to avoid thread suspension skewing the 10s budget.
4. If the worker truly hangs, capture a dump of both threads to inspect the TransactionMonitor lock state.

Example fix

// before
if (!reproObserved.Wait(TimeSpan.FromSeconds(10)))
{
    throw new TimeoutException("Timed out waiting for ReleaseTransaction to finish.");
}

// after
if (!reproObserved.Wait(TimeSpan.FromSeconds(60)))
{
    throw new TimeoutException("Timed out waiting for ReleaseTransaction to finish. " +
        $"Worker alive={worker.IsAlive}.");
}

// Before the repro, assert the engine still owns the transaction on the main thread
var transactions = (IEnumerable<object>)(transactionsProperty.GetValue(monitor));
if (transactions == null || !transactions.Any())
{
    throw new InvalidOperationException("No active transaction to release; repro preconditions not met.");
}

// Repro harness: treat a hang as a soft failure, not a hard crash
ManualResetEventSlim done = new(false);
// ... worker sets done ...
if (!done.Wait(TimeSpan.FromSeconds(30)))
{
    Log(host, "ReleaseTransaction did not finish in time; skipping assertion.", ReproHostLogLevel.Warning);
    return; // or mark the repro inconclusive
}

When it happens

Trigger: Calling ReleaseTransaction via reflection on a thread that does not own the transaction while the main thread holds the transaction open, causing the monitor to block or the reflected invoke to never unwind within 10s. Reproduces only when the TransactionMonitor refuses to release a transaction from a foreign thread by blocking instead of throwing.

Common situations: Running the Issue_2561 repro on a build where the transaction monitor's thread-affinity behavior changed (e.g. it now blocks on a lock rather than throwing), under heavy thread contention, or in a debugger that pauses the worker thread past the 10s budget.

Understand the failure class

• Timeouts: ETIMEDOUT, deadlines, and hung requests — what actually expires when a request times out.

Related errors

• Expected LiteException was not observed.
• LiteException did not contain expected message. Actual: {obs
• Failed to begin primary transaction for reproduction.
• ENTITY_INITIALIZATION_FAILED
• MAPPING_ERROR

AI-assisted analysis of litedb-org/LiteDB@f906a5f850 (2026-08-13). Data as JSON: /api/errors/55696140f2b4d065. Report an issue: GitHub.