It appears the patch mentioned above is just a 
framework to actually do something to remedy the
situation.  Unfortunately it fills the session error
log even faster because it outputs 2 messages every
time there is an XID collision.  :(

Working to see the effect of deleting all events and 
starting from scratch in the event of a collision.




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to