Extend Session Timeout

[frontstrat]

I have an issue that I can't seem to resolve. The Sugar session keeps timing out at the default 24 minutes. The following is from my phpinfo file under the Session section.

session
Session Support enabled
Registered save handlers files user wincache
Registered serializer handlers php php_binary wddx

Directive Local Value Master Value
session.auto_start Off Off
session.bug_compat_42 Off Off
session.bug_compat_warn On On
session.cache_expire 180 180
session.cache_limiter nocache nocache
session.cookie_domain no value no value
session.cookie_httponly Off Off
session.cookie_lifetime 0 0
session.cookie_path / /
session.cookie_secure Off Off
session.entropy_file no value no value
session.entropy_length 0 0
session.gc_divisor 1000 1000
session.gc_maxlifetime 7200 7200
session.gc_probability 1 1
session.hash_bits_per_character 5 5
session.hash_function 0 0
session.name PHPSESSID PHPSESSID
session.referer_check no value no value
session.save_handler wincache wincache
session.save_path C:\PHPTemp C:\PHPTemp
session.serialize_handler php php
session.use_cookies On On
session.use_only_cookies Off Off
session.use_trans_sid 0 0

I am running PHP Version 5.2.13.

I am running sugar in Windows 2003, IIS 6. I also have the following:
extension = php_wincache.dll

Does wincache have anything to do with the session timeout?

I have even modified the Application Configuration "Enable Session State" and set the timeout to 120 minutes.

Is there anything else I can try? This is becoming a pretty big issue with our users.

Any help or direction would be appreciated.

Thanks,
Kevin

[Angel]

Adjust the time by increasing the value of session.gc_maxlifetime in your PHP.INI. Make sure you restart your web service after applying your changes to PHP.INI.

[frontstrat]

Thanks for the reply. Changing the session.gc_maxlifetime to 7200 was the first thing I tried. I was hoping it would fix the issue. Unfortunately, it did not. I restarted IIS several times. I have a server reboot scheduled for over the weekend. We will see if this works.

-Kevin

[frontstrat]

Well, the server reboot did not help. We are still being timed out after 24 minutes. There is only one php.ini file on the server and it has it's session.gc_maxlifetime = 7200. I'm not sure where to go from here. Not sure if this is a Sugar issue or a PHP issue.

-Kevin

[Angel]

I am not familiar with the intricacies of wincache, but perhaps there is a setting associated with its use that is causing the problem.

Are they session files actually removed from the sessions directory when this happens?

[frontstrat]

Not sure about wincache. I'm a windows developer or this whole php/wincache configuration has me at a loss.

I have my session.save_path = "C:\PHPTemp".

There are some old files in this directory. Do you think it is safe to remove these files?

I'm not sure how to cofigure wincache. I do see in the session cache entries that the TTL is 7200.

Thanks,
Kevin

[frontstrat]

Well I have tried every configuration setting that I can find. I have modified my PHP.INI file, the wincache.ttl setting and also the ini file for the FastCGI. Nothing seems to be working to extend the session.

Does anybody know if this issue is specific to running Sugar on a Windows 2003 server? Would changing Sugar over to a Linux server solve this issue? Are there any other benefits to running Sugar on Linux as compared to Windows? Any performance increases?

Thanks,
Kevin

[Angel]

It is not a Windows thing. I have several test installs (as well as customers) on Windows 2003 and they don't have this problem.

However, I have noted quite a bit of chatter on this matter from WinCache users. It might be specific to that.

[frontstrat]

Thanks for the reply. On your other Windows 2003 environments, do you use any sort of cache accelerator like Wincache? If there is another alternative, I may give that a try.

Thanks!
Kevin

[Angel]

I've used eAccelerator and APC on some of them. APC caused some weird behavior at one client's site, but it wasn't related to what you are seeing. I don't remember the exact details, but if I remember correctly, it had something to do with the module builder.

I've never used wincache on any of them. My understanding is that it is Beta, at least the last time I looked, so I wouldn't be surprised if there is some weird thing going on with it.