#33622Filebackend reports error when trying to rename file due to concurrent processes
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.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 2
Files 1
History 12
-
Peter Russ changed attached 33622.patch target version done
0 %80 % <span data-processor="relativetime" data-value="2012-02-02T14:31:33+00:00" > 02/02/12, 14:31 </span> -
Marc Bastian Heinrichs commented <span data-processor="relativetime" data-value="2013-01-31T18:29:53+00:00" > 01/31/13, 18:29 </span>
-
Max Roesch commented <span data-processor="relativetime" data-value="2013-03-11T16:58:16+00:00" > 03/11/13, 16:58 </span>
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.
-
Oliver Hader commented <span data-processor="relativetime" data-value="2013-04-14T12:45:13+00:00" > 04/14/13, 12:45 </span>
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 -
Mathias Schreiber changed target version Is Regression 0 <span data-processor="relativetime" data-value="2015-01-15T11:16:49+00:00" > 01/15/15, 11:16 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2015-06-15T17:44:28+00:00" > 06/15/15, 17:44 </span>
-
Susanne Moog changed target version <span data-processor="relativetime" data-value="2015-08-05T10:28:55+00:00" > 08/05/15, 10:28 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2015-09-24T20:42:38+00:00" > 09/24/15, 20:42 </span>
-
Mathias Schreiber changed target version <span data-processor="relativetime" data-value="2015-10-28T14:47:54+00:00" > 10/28/15, 14:47 </span>
-
Andreas Kienast commented <span data-processor="relativetime" data-value="2024-12-20T14:04:23+00:00" > 12/20/24, 14:04 </span>
This probably sounds like #91768, which has been tackled in the meantime. Therefore I’ll close this issue.
-
Andreas Kienast changed Related to #91768 <span data-processor="relativetime" data-value="2024-12-20T14:04:42+00:00" > 12/20/24, 14:04 </span>
-
Andreas Kienast changed status
NewClosed <span data-processor="relativetime" data-value="2025-01-08T11:31:24+00:00" > 01/08/25, 11:31 </span>
Exception timestamp is 1222361632, right?. Had this already on different systems, too.
Peter, you uploaded the wrong patchfile, aren’t you?