Hi, thanks for the info. I didn't disable the timeout, at least not consciously. ;) What would we have to have done to disable the timeout?
Anyway I'll stay tuned. :) -- Max On 2 Feb., 10:34, Christian Boos <[EMAIL PROTECTED]> wrote: > mb wrote: > > Hi, > > > we have an interesting phenomenon. Sometimes trac just hangs forever. > > The daemon tracd runs, > > tracd makes a heavy use of the db/pool code, which is why bugs in there > can become more "visible". > And despites several attempts to "fix" it, this code is still buggy. > It used to be able to hang completely, but I've added a timeout > (defaults 20 seconds) on the Condition.wait call, so normally this > shouldn't happen anymore. Maybe you've disabled the db timeout? > > I'm currently investigating the "interesting" behavior tracd shows when > it has to deal with number of concurrent requests that is higher than > the number of available connections in the pool, so stay tuned ;-) > > -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
