The global `gAbortExpiredTransactionsSessionCheckoutTimeout` is a global int. Command setParameter references this int through the `IDLServerParameterWithStorage` type, which effectively wraps the global in a mutex. When the `PeriodicThreadToAbortExpiredTransactions` thread references the global, it is unprotected because it does not go through the `IDLServerParameterWithStorage` type.

Other IDL parameters that can be changed at runtime typically use an Atomic. This means that there's 2 forms of synchronization here (`IDLServerParameterWithStorage`, atomic global) which is not ideal, but I think we can just follow the precedence here considering the changes are not performance sensitive.