Current implementation is crude and can only correctly support one call site for lockTxnNumber(), specifically it will be unsafe to call unlock() if lockTxnNumber is called in more than once place because it can unintentionally unlock something it shouldn't.