Bug #16538 Updated: session data not consistently stored during startup (10-50% failure rate)
| From: | jerry dot zhao at vanderbilt dot edu | Date: | Sat, 04 May 2002 14:27:39 +0000 |
| Subject: | Bug #16538 Updated: session data not consistently stored during startup (10-50% failure rate) | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-6907@lists.php.net to get a copy of this message | ||
ID: 16538
Updated by: jerry.zhao@vanderbilt.edu
Reported By: jerry.zhao@vanderbilt.edu
-Status: Feedback
+Status: Open
Bug Type: Session related
Operating System: Solaris 7
PHP Version: 4.1.2
New Comment:
You are right! I was returning a boolean false instead of "". Now
everything works as it should be. Thanks!
Previous Comments:
------------------------------------------------------------------------
[2002-05-02 10:21:45] yohgaki@php.net
As in Manual, you are supposed to return string type always from read
function. Did you do that?
------------------------------------------------------------------------
[2002-05-02 10:03:03] jerry.zhao@vanderbilt.edu
I fixed the session problem by replacing all boolean values with "1" or
"0" in the user defined session functions.
There were still some "bus error" errors and other httpd process
related issues, which went away after we upgraded to the latest Apache
1.3.24.
------------------------------------------------------------------------
[2002-04-11 06:22:43] sander@php.net
To properly diagnose this bug, we need a backtrace to see what is
happening behind the scenes. To find out how to generate a backtrace,
please read http://bugs.php.net/bugs-generating-backtrace.php
Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open".
------------------------------------------------------------------------
[2002-04-10 16:57:07] jerry.zhao@vanderbilt.edu
We use mysql db as the store for session data. In the past one month or
so, I have noticed that Apache generated some "Segmentation fault" or
"Bus error" messages. I was finally able to single out the cause of
these errors: a couple of php pages using session. When a new session
is initiated, the session data is not stored in the mysql db at least 1
out of 5 times, which appears to be related to the segfault/bus errors.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=16538&edit=1