Re: bug in xaraya PHP session save handler

Marcel van der Boom wrote:
> 2. race conditions / locking / customisations
> ---------------------------------------------
> These problems are more fun :-)
> 
> These typically only surface when you have a heavily used site or are 
> explicitly looking for these things. The average user doesnt get (hurt 
> by) these problems (hopefully)
> The second reason that these situations are hard to solve in a generally 
> applicable way, is that they all depend heavily on the local deployment 
> choices. Backend type and configuration, proxies and other local 
> optimisations.
> 
> For example, the locking solution chris described is likely the easiest 
> for them, but when using persistent connections the solution might not 
> work anymore and something else has to be figured out. This is indeed 
> typically something that would go in the middleware layer (ADODB)
> 
>> happy to help explain the problem in more detail.  We'd like to see 
>> this bug placed in Bugzilla so that it can eventually be addressed. 
> I'll make sure it gets there
> 
> Marcel

I'm actually experiencing this issue on a high-traffic client site. I am 
looking for anyone that would like to use the environment to research 
this particular issue.

The symptoms seen by users include being suddenly switched to a 
different user's account (ie: session UID changes) or they post 
something that gets listed as by a different user (either in articles or 
comments).

Also looking for any advice. I have implemented the locking snippets 
submitted originally in this thread, and will report back if they do not 
resolve the issue.

Affected site: http://www.ruminations.com

-St.Ego