You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There might be environments where the key store file might be shared either
by multiple MTMs in multiple processes, and/or
by MTM and other libraries.
In both cases, thread synchronization within MTM is not enough. So I suggest to use file locking (if available on the platform and for the key store location) to prevent concurrent file access: a shared lock for reading and an exclusive lock for writing.
The text was updated successfully, but these errors were encountered:
rfc2822
changed the title
Use file-locking mechanisms for multi-process environments
Use file locking mechanisms for multi-process environments
Jul 12, 2016
Maybe there should also be a mechanism to notify MTMs in other processes when the key store has changed (so that keyStoreUpdated() can be called).
Alternatively, the key store could be loaded for every request. (Maybe as an option, so that only multi-process enviroments have to do that.) However, I don't know the real performance implications. Maybe we should have a look how other multi-threaded or multi-process applications use the KeyStore.
There might be environments where the key store file might be shared either
In both cases, thread synchronization within MTM is not enough. So I suggest to use file locking (if available on the platform and for the key store location) to prevent concurrent file access: a shared lock for reading and an exclusive lock for writing.
The text was updated successfully, but these errors were encountered: