On Tue, 2008-04-08 at 00:46 +0200, Henrik Nordstrom wrote: > 7. Watch both events trigger, get AsyncCall queued and smash each other > even if the pconn code tries to do things right and deregister one if > the other trigger...
... > The workaround is simple, verified and committed. Make the assert a soft > error. It's harmless. But I seriously think we need to revisit the async > call queue a bit to see how this kind of situations is meant to be dealt > with. It's not the first bug of this kind caused by the queue.. > > my immediate reaction is that cbdata should be used proper, with one > cbdata per state machine. I.e. in this case one cbdata per idle pconn > and not just one per pconn host... Can you post cache.log lines with full debugging enabled? I would be happy to help with the queue review, but it would speed things up if I do not have to go through the complicated steps required to reproduce the problem. Thank you, Alex.
