After reviewing this, I think we don't need to fix it when using the file store. The whole idea of the file store is to provide a simple storage, not intended for production or complex environments (eg.: using clustersm clusters, shared file system, etc).
Due to its limitations, FileIdentityStore can be used in a limited capacity. It can not be used on shared file system (such as NFS and Windows shares) due to a lack of proper file locking, resulting in data corruption. Furthermore, file systems are not inherently transactional, resulting in file writing failures during the commit phase if the cache is used in a transactional context.
For this specific case, I think that a JPA store would be the best option, as suggested.
|
