Am 27.06.2006 um 18:15 schrieb Stephen Deasey:
There's no default timeout in the current code, and the error message should be:timeout waiting for concurent update: ... Make sure you're testing code from HEAD.
Easier said than done. The HEAD is not usable for testing as the code we have on the customer site is dated prior to your recent changes to ns_cache. Hence I must look in the code before that and try to understand if there is still something wrong OR the timeout of 3 seconds is just to low. We will have to maintain a separate internal branch until all this noise on ns_cache settles down and we are again all confident that it works as wanted/expected. Recent changes made it incompatible with the rest of the code and we can't make changes there for some time. Cheers, Zoran
