Project

General

Profile

Actions

Bug #86941

closed

Logger instances in scheduler tasks are deserialized with outdated paths

Added by Helmut Hummel over 5 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2018-11-16
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Scheduler serializes tasks and stores them in the database.
If these tasks store a logger instance (e.g. by using the LoggerAwareTrait), this instance will be serialized as well and will point to the wrong path, e.g. when TYPO3 is moved to a different folder
or path changes due to deployments.

This issue became much more prevalent with the addition of LoggerAwareTrait to \TYPO3\CMS\Scheduler\Task\AbstractTask
Now every single task will store outdated logger instances pointing to very likely broken directories


Related issues 4 (0 open4 closed)

Related to TYPO3 Core - Bug #87094: A Symfony Console based scheduler task can't be executed and breaks the scheduler moduleClosed2018-12-07

Actions
Related to TYPO3 Core - Bug #87261: Upgrade wizard for scheduler tasks with invalid Logger instance pathsClosedJoerg Boesche2018-12-21

Actions
Related to TYPO3 Core - Bug #87780: Extbase Task should call parents __sleep and __wakeup MethodsClosed2019-02-25

Actions
Related to TYPO3 Core - Bug #86785: Calling scheduler command on CLI throws error if not in /var/www/htmlClosed2018-12-21

Actions
Actions

Also available in: Atom PDF