ID: 5652 Fixed in:
Issue Date: 2009-07-29 21:50 AEST Owner:  CVS Support
Last Modified:  2009-07-29 21:50 AESTReporter:  Arthur Barrett
Current Est.  0.0 hours % Complete:  0.0  
Status:NEW / Severity:normal

Affected:  2.5.03
Description:  lock conflict wait should be randomised

Actions:    
2009-07-29 21:50 AEST by Arthur Barrett - lock conflict wait should be randomised - when a read lock or write lock fails, rather than wait 1/5th 
second - use a more random value to help processes not end up 'synchronising'.


     Query page