The issue is that once in awhile a webpage that creates to some Session may cause apache to hold forever for the session. Once this error happens for just one user any more modifications to the session associated with a user may cause the web site to hold with this user.

This issue continues to be my sole focus for the days. I've got a development VPS running Home windows 2003 and default latest version of XAMPP while using standard PHP session handler. The code under consideration really operates on two other machines perfectly normally so although my good sense states it’s an internet server configuration problem but at this time I'm prepared to try anything.

On further analysis you will find no errors within the Apache, PHP or System event log. Assets are abundant and there's no “AJAX shit storm” or greater than a couple creates to some session per page. I've also implemented session_write_close() whenever we can to help elevate the issue.

I've checked the session’s directory that is set to “C:windowsTemp” and located that when a person makes its way into this hanging phase the corresponding session file is solely locked and the only method to resolve this really is to prevent Apache and wait a couple of moments for that files being unlocked and remove them. I'm not wondering if deletion is needed.

The Periods themselves only contain 4 items of information. ShoppingCartID, UserID, UserLevel and Refering URL and therefore are alphanumerical by having an periodic slash.

My PHP.INI’s session section is set up such as this:

session.save_handler = files
session.save_path = "C:\WINDOWS\Temp"
session.use_cookies = 1
session.name = PHPSESSID
session.auto_start = 0
session.cookie_lifetime = 0
session.cookie_path = /
session.cookie_domain =
session.cookie_httponly =
session.serialize_handler = php
session.gc_probability = 1
session.gc_divisor = 100
session.gc_maxlifetime = 1440
session.bug_compat_42 = 1
session.bug_compat_warn = 1
session.referer_check =
session.entropy_length = 0
session.entropy_file =
session.cache_limiter = nocache
session.cache_expire = 180
session.use_trans_sid = 0
session.hash_function = 0
session.hash_bits_per_character = 4

I've attempted everything I'm able to think about and also the whole issue is now a blur in my experience. Any ideas could be appreciated and interesting time reading through this :)

It may be your session files getting locked by Home windows or some php.ini configurations dirty correctly. Please SEE HERE

Almost am getting at it is the lock files.

Is it feasible your application internally demands a webpage in the same site again internally? You may be striking a race condition of sorts where page A fires up, locks the session, after which in some way triggers a request to itself, or page B, that also attempts to re-start the session, that is now locked, and also the request dangles.

Otherwise, when the hang is triggered through the session file being locked, I'd suggest using something similar to SYSInternal's 'Handle' to obtain a listing of the items processes are utilizing the session file under consideration.