Project

General

Profile

Actions

Bug #70105

closed

Unsuccessful scheduler task execution results in "Serialization of 'Closure' is not allowed" error

Added by Joschi Kuphal over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
scheduler
Target version:
Start date:
2015-09-25
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
5.5
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

As of TYPO3 CMS 7.4, returning FALSE from a scheduler task's execute() method results in a "Serialization of 'Closure' is not allowed" error, locking the task for future executions. I tracked this down to the serialization of the exception that is thrown by the scheduler when logging it to the database (\TYPO3\CMS\Scheduler\Task\AbstractTask::unmarkExecution() line 427). It seems to be the topmost closure that's used in typo3/index.php to start the whole application which is disrupting the serialization.

This means, there's currently no way of gracefully ending an unsuccessful task execution. You either have to return TRUE to not block the task for future executions, or you'll have to unlock it manually after each run.


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #69157: scheduler serializes complete exception on task failureClosed2015-08-18

Actions
Actions #1

Updated by Stephan Großberndt over 8 years ago

  • Status changed from New to Closed

Fixed in TYPO3 7.5 and 6.2.15

Actions

Also available in: Atom PDF