Project

General

Profile

Actions

Bug #16619

closed

Fail-safe mechanism for database connectivity problem

Added by John Angel about 18 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2006-10-04
Due date:
% Done:

0%

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

Description

1/ All pages should be exported to static HTML pages on regular basis (incrementally & automatically)

2/ If Typo3 detects database connectivity problem - it should display static HTML pages previously exported in step 1.

The same idea can be used to run website powered by Typo3 faster. Step 1 can be run in background after some page is being created/updated.

(issue imported from #M4332)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #22463: Add a method to check if database is connectedClosedDmitry Dulepov2010-04-15

Actions
Actions #1

Updated by Michael Stucki about 18 years ago

If you end up with a database connection error, the reason for the problem might be somewhere else:
Either the server has too limited resources available, or the database connections are not closed correctly by PHP.
So you should try to investigate this problem a little more.

Additionally, the "fail-safe" mechanism you have mentioned is possible already by using the [FE][pageCacheToExternalFiles] option in TYPO3s Install Tool.

Closing.

Actions #2

Updated by John Angel about 18 years ago

I am using pageCacheToExternalFiles=TRUE.

When I stop mysql server, Typo3 displays: "Database Error; The current username, password or host was not accepted when the connection to the database was attempted to be established" instead of real page.

Actions #3

Updated by Michael Stucki about 18 years ago

Yes I know. Please see my last comment: TYPO3 has a problem connecting to the database.
You are using the file-cache feature but still get the error because there are still some parts on your website which cannot be cached. They will require database connections for every request, independent of your cache settings.
To dig more into this problem, please enable database logging and check what queries are being executed...

Besides of this I would like to ask you to not reopen bugs again and again. The bugtracker is probably not the right place for discussions like this or in #0002673. So if you disagree with the resolution change of one of the developers, please do not change it again unless you have assured that the problem really exists. I suggest you start a discussion on typo3-dev for things like this....

Actions #4

Updated by Michael Stucki about 18 years ago

One more note about this: Parts like the search engine which are purely dynamic can never be cached and would never work without a database access. In this case, the fail-safe mechanism idea is not a perfect solution anyway...

Actions #5

Updated by John Angel about 18 years ago

Since it cannot connect to database, it has to display exported HTML, no matter what.

Actions #6

Updated by Chris topher over 14 years ago

Stucki said it all.

Actions #7

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF