ID: 32897 User updated by: dmih at in-solve dot ru Reported By: dmih at in-solve dot ru -Status: Feedback +Status: Open Bug Type: Session related Operating System: Win32/all PHP Version: 4.3.10 New Comment:
I just want to solve this issue, please understand. I'll upgrate one server to 4.11 now. I'll tell if this happens there. bug http://bugs.php.net/bug.php?id=25876 was seen by people quite often. Please anyway tell me how can I tell reproduce code if it happens after hours of heavy load, with low probability? Is there any strategy for this? Please tell me, if I do not find how to reproduce it, you will not pay attention to this? Thank you. Previous Comments: ------------------------------------------------------------------------ [2005-04-30 11:57:33] [EMAIL PROTECTED] 1) Upgrade to the latest version first. 4.3.10 is NOT the latest version available. 2) Instead of complaining and telling how many customers you have please tell how to reproduce it because none of us is able to reproduce it till now. ------------------------------------------------------------------------ [2005-04-30 11:45:47] dmih at in-solve dot ru 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. ------------------------------------------------------------------------ [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; } ------------------------------------------------------------------------ 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
