From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
This is a random problem. Being said that I'll describe what's happening...
I recompiled the php component as told in BUG#143183 to enable Informix and OCI8 support, and as my application that shows this behavior depends on them, I am unable to test with the plain component as shipped from RedHat. That's what happens:
The sessions created expired at random times, not following the configuration in php.ini. Sometimes it's much too earlier, sometimes too later, but the most important fact is that they don't seems to follow the interactions of the users, since the expiration period is based on lack of user interactivity with the server. Everytime the expiration occurs on some almost constant amount of time, being the user interacting or not with the server. I found no solution nor work-around for this yet.
The second behavior that we got is that sometimes the session doesn't seem to be initialized, but no notice, warning or error is given (I tried using E_ALL error reporting). The most intriguing part is that only some random client machines show this problem (I belive that it's because only some httpd processes were affected). The only thing to do to resolve this issue is to restart the httpd process.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Any news on this subject??? I'd tried to control the session expiration by hand,
setting a multi level depth for the session storage and putting in cron a script
to clear the files that where last accessed 30 minutes.
The problem is that even with this setting the session expires randomly.
Only to confirm, the session files were generated in the tree hierarchy just
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.