ID: 24295
User updated by: marcus at quintic dot co dot uk
Reported By: marcus at quintic dot co dot uk
Status: Open
-Bug Type: Documentation problem
+Bug Type: Session related
Operating System: Windows XP
PHP Version: 4.3.2
New Comment:
File size seems not to matter - its a really annoying bug to try and
reproduce as well. One day I'll have no problems at all, the next its
falling over all the time. If I watch the apache logs there are no
errors and once its locked no documents are being requested. If I
switch on the php error logs nothing appears in there either. Is there
anyway I can get more debug information? Its like a page is getting the
session lock and not giving it up and so stopping all other pages from
starting (because they all try to get the session).
Whats wierd is that nothing gets put in the apache access log - I can
click on a button in one of the frames that launches a new window
(using javascript) that I know requests a certain php document (again,
under the same session), but the request never makes it into the access
log and the document never gets to the window.
I think the original reply (after my submission) switched it to
documentation - I've switched it back to session related.
Previous Comments:
------------------------------------------------------------------------
[2003-06-23 08:15:40] [EMAIL PROTECTED]
Sorry, 'use_trans_sid' of course ( shoudln't have written the reply in
a hurry..)
Whats the size of the files in question anyway?
Does it work more reliable with small(er) files?
I still don't the a documentation issue here..?
------------------------------------------------------------------------
[2003-06-23 07:58:41] marcus at quintic dot co dot uk
wrt disabling session.enable_trans_sid
Assuming you mean the use_trans_sid option, its already disabled.
------------------------------------------------------------------------
[2003-06-23 06:56:53] [EMAIL PROTECTED]
Disable
session.enable_trans_sid
in php.ini or by <Files filename.php>-Entry in http.conf and see if
your problem is gone.
------------------------------------------------------------------------
[2003-06-23 06:16:19] marcus at quintic dot co dot uk
Mmmm - I may not have made myself clear enough in the bug report! By
lockups I meant that the _whole_ session locks completely and never
comes back to life. Once a frame gets into this state, none of the
other frames will work and the browser appears to be completely locked
up.
A new instance of the browser works as normal though (different
session).
------------------------------------------------------------------------
[2003-06-23 06:11:42] marcus at quintic dot co dot uk
Eh? I realise the session file should be locked to restrict access,
what I dont expect is the browser to lockup completely.
If any of the pages are requested/executed at the same time then surely
each of the frames should just go about their business, wait for the
session file lock to come free and continue to work. Whilst this may
delay some of the documents it shouldnt be significant. It certainly
shouldnt lock up the browser completely.....
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/24295
--
Edit this bug report at http://bugs.php.net/?id=24295&edit=1
