Bug #42111

Lockfiles retain on sql error, no further versioning is possible for affected record in the fututer

Added by Michael Schramm about 7 years ago. Updated about 4 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2012-10-18
Due date:
% Done:

0%

TYPO3 Version:
4.5
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

if you try to publish a page and i.e a sql error occurs there will be retain a lockfile for this page so that even if the error is removed the file stays locked in PATH_site.'typo3temp/swap_locking/ an can't be published

\typo3\sysext\version\class.tx_version_tcemain.php
...
// Lock file name:
$lockFileName = PATH_site.'typo3temp/swap_locking/' . $table . ':' . $id . '.ser';

if (!@is_file($lockFileName) )    {
...

After deleting the lockfile in PATH_site.'typo3temp/swap_locking/ everything works fine again

Is ist for example possible to add a max lifetime to the lockfile and request in like
if (!@is_file($lockFileName) && $maxLockFileLifetime > now() ) {

History

#1 Updated by Michael Stucki almost 6 years ago

  • Category changed from Bugs to Workspaces

#2 Updated by Michael Stucki almost 6 years ago

  • Project changed from Workspaces & Versioning to TYPO3 Core
  • Category changed from Workspaces to Workspaces

#3 Updated by Mathias Schreiber almost 5 years ago

  • Target version set to 7.5

#4 Updated by Benni Mack about 4 years ago

  • Target version changed from 7.5 to 7 LTS

#5 Updated by Mathias Schreiber about 4 years ago

  • Target version deleted (7 LTS)

Also available in: Atom PDF