Project

General

Profile

Actions

Bug #65591

closed

Various caches not cleared by "clear all cache"

Added by Stefan Neufeind about 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2015-03-08
Due date:
% Done:

0%

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

Description

Even when doing a "clear all cache" from install-tool some caches are not cleared. This showed up when a memcache-backend was defined for "extbase_reflection". The flush-method was never called.

CacheManager passes the flushCaches() on to all Cache-frontends which call flush for their backend.

In typo3/sysext/install/Classes/Controller/AbstractController.php, loadBaseExtensions() various caches (including extbase_reflection) are defined with a NullBackend.

Defining a "dummy"-cache with memcache-backend unfortunately also didn't trigger a clear, since the cache-identifier is part of the tag to be flushed.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #65406: extbase_reflection cache not cleared with ApcBackendClosed2015-02-27

Actions
Actions #1

Updated by Christian Kuhn almost 9 years ago

could you re-test this scenario on master? imho extbase reflection cache should be properly cleared there, also if apc / memcache is used. if it works on master, we should figure out which patches are left for 6.2 if the issue persists there.

Actions #2

Updated by Christian Kuhn almost 9 years ago

  • Status changed from New to Needs Feedback
Actions #3

Updated by Alexander Opitz over 8 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions #4

Updated by Stefan Neufeind over 8 years ago

I wasn't able to test this again, with the project we experienced problems with (and needed to implement a different solution at that time).

With Christian I lately talked about the issue as well. He said that putting the extbase_reflection-cache somewhere else (memcache in our case) really means calling for serious trouble. Unfortunately some caches need to be overridden with an early-cache-configuration. That's why this special cache can't be cleared since at that point.

Actions

Also available in: Atom PDF