Bug #33622
openFilebackend reports error when trying to rename file due to concurrent processes
80%
Description
Due to concurrent processes it happens that a temp-cache-file gets renamed while an other process is just writing it.
Further there is an error in the error handling.
- added an exclusive lock for the writing operation
- added counters for a break to avoid an endless loop due to file system errors
- added timers for getting the process to sleep
- fixed error handling
As this is the same in FLOW3 I also reported the bug and fixes there.
see http://forge.typo3.org/issues/33621
Please find TYPO3 specific fixes attached.
Files
Updated by Peter Russ over 12 years ago
- File 33622.patch 33622.patch added
- Target version set to 4.5.12
- % Done changed from 0 to 80
Updated by Marc Bastian Heinrichs over 11 years ago
Exception timestamp is 1222361632, right?. Had this already on different systems, too.
Peter, you uploaded the wrong patchfile, aren't you?
Updated by Max Roesch over 11 years ago
Just stumpling upon this on a TYPO3 6.0.4 installation at Hosteurope.
Core has the patch from FLOW3 but nevertheless I am running in the same error.
Updated by Oliver Hader over 11 years ago
The cache file ".../t3lib_l10n/3e2cbbda0301cf592e5831ef26c56b7b" could not be written.
This issue has been solved on concurrent editing actions in the backend for 4.7, 6.0 and 6.1 in issue #46205
However, that does not solve the original issue in the FileBackend that probably needs to be solved by locking mechanisms
Updated by Mathias Schreiber over 9 years ago
- Target version changed from 4.5.12 to 7.3 (Packages)
- Is Regression set to No
Updated by Benni Mack about 9 years ago
- Target version changed from 7.3 (Packages) to 7.4 (Backend)
Updated by Susanne Moog almost 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack almost 9 years ago
- Target version changed from 7.5 to 7 LTS