Bug #87820
closed
Logger not instanciated in cache backend
Added by Marco Dinnbier almost 6 years ago.
Updated almost 5 years ago.
Description
The function setLogger is never called in cache backend.
The cache backend is instanciated via 'new' and not via GeneralUtility::makeInstance in TYPO3\CMS\Core\Cache\CacheManager::createCache.
This leads to an error, when the logger in cache backend class is needed: 'Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function alert() on null ...'
Hmm, this is a tricky one.
Basically, because AbstractBackend is a LoggerAwareInterface, basically all caches that are used until ext_localconf.phps are loaded (cache_core, assets) will not have their final Logger Configuration set. We can add this manually, which would make sense, but this might result in more side-effects...
But the solution for this patch would be: createCache() checks for the LoggerAwareInterface and puts in the code, like makeInstance does it.
- Has duplicate Bug #88775: logger in ApcuBackend is not instantiated added
This bug is a showstopper.
We've got redundant server nodes. If one node is down the website is still online.
But if the Redis-Server is down (for maintenance e.g.), the webside is down too.
- Target version set to next-patchlevel
- Status changed from New to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Related to Bug #88938: wrong class statement for logger initialization added
- Status changed from Resolved to Closed
Also available in: Atom
PDF