ID: 20449
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Session related
Operating System: redhat 7.3
PHP Version: 4.4.0-dev
New Comment:
Back again, with new informations !
I have setup a small test platform, with custom session handlers to a
database, and DBMS in debug mode.
When I force a session write before the end of the script, I get the
whole session var serialized.
When I force a sess_write_close at the same place, I get a truncated
serialized session var (objects missing)
When I let things behave normally, I get a truncated serialized session
var (objects missing)
Thus, I have an hypothesis : The objects inside the session var are
destroyed _before_ the serialization occurs, leading to a truncated
result.
Could you please revert back to me with more on this ?
Previous Comments:
------------------------------------------------------------------------
[2002-12-05 06:22:50] [EMAIL PROTECTED]
Well, a few checks later, the serialize function is working on my
session var (tested just before the end of the script)
Also, there is no detectable concurrent save of the session, as the
main script is executed only once, while the iframe is run each time.
------------------------------------------------------------------------
[2002-12-05 05:52:52] [EMAIL PROTECTED]
Could possibly be related to Bug #17419 (cross referenced classes are
not supported by the serialization function) ?
------------------------------------------------------------------------
[2002-12-05 05:46:12] [EMAIL PROTECTED]
Well, I have the same kind of problem (I try to upgrade from 4.0.4pl1 -
I know I should have done this before)
In my case, I use an iframe to display the results of a search. You can
select the page by clicking a number.
This works well with 4.0.4pl1, not with 4.1.7 or 4.2.2
After some searches, I've finally found out that my session was not
correctly saved (neither in a file nor in a db, I tried both)
I tried to force the write of the session with no better results.
As my session var contains an object, I also suspect the serialize
handler.
Another possibility is two instances trying to write the session at the
same time (I use the session both in the main page and in the iframe)
At present, I'm wondering if using the wddx serialization would be
better.
I hope this will help to fix the problem.
Regards,
------------------------------------------------------------------------
[2002-12-04 14:04:05] [EMAIL PROTECTED]
Our objects are fairly complex. Objects w/ local (as much as they can
be) objects and plenty of our friend - the assoc. array.
I was unable to reproduce this issue on my own (maybe you will have
better luck) even though on a normal day I can watch syslog chime out
unserialize errors.
I'd be more then happy to send a session, class definitions, etc. if
needed. Shoot me an e-mail if you need anything.
------------------------------------------------------------------------
[2002-12-04 12:26:50] [EMAIL PROTECTED]
Hmm..
I'm going to see if I can't reproduce this bug in some form, starting
from the serialize() function... it's possible that serialize() isn't
doing things correctly.
Is this just a array problem? Or has someone also found this error in
objects that don't use arrays?
I'm going to write up some test scripts and see if I can break
serialize()... I'll post my results here.
------------------------------------------------------------------------
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/20449
--
Edit this bug report at http://bugs.php.net/?id=20449&edit=1
