Bug #41362
closedconnectDB() does not signal connection problems to scheduler
0%
Description
I had the case that the credentials in localconf.php where dependent on an environment-variable. Not passing this variable to scheduler resulted in failing connections to the database (obviously) but the scheduler didn't tell any problems except for the return code 1 instead of 0.
This could be easier…
The thrown exceptions do not show in the cli-environment, therefor a switch could be added to use a die($message) when in cli-mode.
Updated by Stefan Galinski about 12 years ago
Sounds like you already know the code that is required to change this behaviour. Can you please create a patch and push it to the review system?
Updated by Gerrit Code Review about 12 years ago
- Status changed from New to Under Review
Patch set 1 for branch TYPO3_4-7 has been pushed to the review server.
It is available at http://review.typo3.org/15045
Updated by Alexander Opitz about 11 years ago
- Status changed from Under Review to Needs Feedback
It seams the issue exists only in the TYPO3 CMS 4.7 series for which the patch set was abandoned.
So I would like to close this issue, is that ok?
Updated by Andreas Lappe about 11 years ago
I thought it still exists in the 6.1 series too, but go ahead and close it… I worked my way around, as in so many other areas of this CMS.
Updated by Wouter Wolters about 11 years ago
- Status changed from Needs Feedback to Closed
- Is Regression set to No
Thanks for your response. Closed.
Updated by Andreas Lappe over 10 years ago
Same problem exists in 6.2… still annoying.