[TYPO3-dev] Problem with Unlink lockfile

[Georg Schönweger]

Hi,

i just noticed that a certain page took really long to load (about 50
seconds). After debugging, deinstalling all extensions ecc., i started
to debug the core (4.5 LTS). The problem was that there was a lockfile
for this page, and because i have max_execution_time set to 2 hours
(needed for another project), the lockfile didn't get deleted for this 2
hours.
If there is no surfer who will wait > 50seconds till the page is loaded,
the page will never land in the cache and as consequence the page is not
available for this 2 hours, really bad...

Now i'm asking myself;
a) how could this happen that the lockfile did not get deleted from the
process who created the lockfile.
b) how often can this happen

Does someone have experience / advices regarding this issue?

I found this in Install Tool;
lockingMethod: "String: Define which locking mode is used to control
requests to pages being generated. Can be one of either "disable" (no
locking), "simple" (checks for file existance), "flock" (using PHPs
flock() function), "semaphore" (using PHPs sem_acquire() function).
Default is "disable"."

Here it says that default would be "disable", but this is not the case.
I checked Typo3 4.5 and Typo3 4.6, default lockingMethod is "simple".
What are the side-effects when i switch to lockingMethod "disable"?


regards,
Georg