I'm running the latest test build of BigBrother (because nothing else works with 1.4 yet!) and noticed it never closes it's SQL connections. When a server is getting a lot of updates, this causes as many as 2,000 left over sockets, in the TIME_WAIT state.. This number will grow as the server is up, causing resources to become exhausted.
I'm running the latest test build of BigBrother (because nothing else works with 1.4 yet!) and noticed it never closes it's SQL connections. When a server is getting a lot of updates, this causes as many as 2,000 left over sockets, in the TIME_WAIT state.. This number will grow as the server is up, causing resources to become exhausted.