> Am 24.11.2015 um 12:45 schrieb [email protected]: > > Most commonly it happens when allocating memory fails. That throws an > exception, which is caught, and then a possibly guilty connection is closed, > some memory deallocated and life hopefully goes on. Except that if the wrong > connection is closed the memory situation may not improve... I want to close > the oldest connection in addition to the current choice, but haven't written > the code to do that yet. I observe this mostly after some network problem with long running connections. Has it to do with TCP error handling? Could some kind of (TCP) keep alive improve the diagnosis of 'guilty connection‘?
Axel --- PGP-Key:29E99DD6 ☀ +49 160 9945 7889 ☀ computing @ chaos claudius
