ID: 32897
User updated by: dmih at in-solve dot ru
Reported By: dmih at in-solve dot ru
-Status: Bogus
+Status: Open
Bug Type: Session related
Operating System: Win32/all
PHP Version: 4.3.10
New Comment:
Please set it to bogus once again to indicate that I am really wrong,
that will clearly tell me that I should just wait without additional
comments/reports.
(that will be disapointing)
I just want to note that previous bug is reproducable, this - not
(random bug). These bugs may be related, but not the same surely.
Previous Comments:
------------------------------------------------------------------------
[2005-04-30 11:39:32] dmih at in-solve dot ru
Please kindly comment this:
---------
[EMAIL PROTECTED] sais:
I don't see how this relates to my problem besides the error message.
I
ask you guys kindly to open a new report about your specific problem.
Your problem has no relation to session handler loosing when calling
session_destroy.
---------
That is, [EMAIL PROTECTED] will say it again - "you do not call
session_destroy".
So this should be separate bug, I guess.
Please understand me; I am reporting and commenting this bug for 3
months already. Our customers of 3 most loaded servers feel stupid
because of this bug.
I do not want this bug to be ignored just because you think that it is
related to call to session_destroy or whatever - there is no need for
this call for this bug to happen.
_Another_ report is bogus, I believe.
------------------------------------------------------------------------
[2005-04-30 11:34:22] dmih at in-solve dot ru
I see that I should not post this bug again, please forgive me.
I just wanted to mark somehow that it is much simplier to reproduce. I
am also developer and I am used to post another bug if bug reproduction
alters a lot.
------------------------------------------------------------------------
[2005-04-30 11:28:55] dmih at in-solve dot ru
It seems that this code fails to get proper handler setting.
/* Open session handler first */
if (PS(mod)->s_open(&PS(mod_data), PS(save_path), PS(session_name)
TSRMLS_CC) == FAILURE) {
php_error_docref(NULL TSRMLS_CC, E_ERROR, "Failed to initialize
storage module: %s (path: %s)", PS(mod)->s_name, PS(save_path));
return;
}
------------------------------------------------------------------------
[2005-04-30 11:28:07] [EMAIL PROTECTED]
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same.
Thank you for your interest in PHP.
As you said, this is same as bug #32330 (why did you have to report
this again?)
------------------------------------------------------------------------
[2005-04-30 10:46:23] dmih at in-solve dot ru
I said that bugs may be related to some apache working process thread.
I may add comment that will make clear why I feel so.
These bugs appearence pattern:
1. 10+ hours - apache working process is running, no bugs at all
2. something happens - I see these errors every 10 minutes or so.
3. apache working process restarts - still no bugs for 10+ hours.
------------------------------------------------------------------------
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/32897
--
Edit this bug report at http://bugs.php.net/?id=32897&edit=1
