Bug #22461
closedRuntimeException thrown within the exception handler when wrong database credentials
0%
Description
Problem:
With patch #22420: Do not die, be the exception!, most of the die() functions are replaced with proper exceptions.
When the database credentials are wrong, a RuntimeException is thrown in class t3lib_db, function connectDB(). The exception handler itself tries to connect to the database as well, in t3lib_error_AbstractExceptionHandler function writeLogEntries(), using this same function connectDB(), for storage in the devlog and sys_log table. This causes recurring RuntimeExceptions, which leads to the Fatal error: Exception thrown without a stack frame in Unknown on line 0
Solution:
Wrap the part in t3lib_error_AbstractExceptionHandler > writeLogEntries() which handles the database actions in a try/catch block, where the catch is simply empty.
(issue imported from #M14117)
Files