On 6/27/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Am 27.06.2006 um 13:33 schrieb Zoran Vasiljevic: > Hi ! > > I got the same report from customers: > > timeout waiting for update: 59331.0.n.childs > > We never use anything except ns_cache_create, ns_cache_flush > and ns_cache_eval commands. This might be if the default value of cacheTimeout of 3 seconds is simply too low for the operation of caching the element in ns_cache_eval. I believe that this default value is too low. I have instructed the customer to increase the value from 3 to 60 secnds and observe the operation. At the same time I'm analyzing the code once more... Soon I will know everything by heart..
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.
