Feature #121
Abort idle transactions on timeout
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
fixed
Description
If a client goes away while holding the write lock, the write lock is
never released, leading to mulgara being locked forever. Currently the
timeout "only" sets the timeout on the internal transaction manager
which just causes the transaction to be marked for rollback on a
timeout. However, setting the timeout should also start a timer which
is used to abort a non-active transaction (this should happened for
both read-write as well as read-only transactions as the latter could
be holding on to a phase, leading to a "memory leak").