On 1/9/13 11:59 PM, Vladyslav Bachynskyi wrote:
Hi,
Sorry for so late reply.
I need to keep that variable so large, because I'm using TS as a cache
for Video on Demand content, and I don't want connection be closed
during movie playing.
Maybe I misunderstood you. It sounded like the problem occurs when the
config is set to 0 ? That's why I'm wondering what is going on, because "0"
means to never close down those connections (in timeouts, 0 means 'infinite').
If you solution to the problem is to set it to "0", then it makes sense.
-- Leif
Thanks,
On 03.01.2013 17:03, Leif Hedstrom wrote:
On 1/3/13 12:36 AM, Vladyslav Bachynskyi wrote:
Hi,
I've Found the root cause.
I have had to many CLOSE_WAIT connections because I've set
proxy.config.http.transaction_active_timeout_in to 0.
By changing this variable the issue has been solved.
I thought, as such connections are not active, they should be fully
closed even without transaction_active_timeout_in...
Hmmmm. That seems somewhat odd that it'd help. It'd be interesting to
look into why (that setting is necessary to keep at 0 for e.g. very
large files (streaming media for example, or YouTube proxy/caching).
Or alternatively, keep it very large (certainly much larger than
120s). What did you set it to ?
What is the problem having connections in CLOSE_WAIT anyways? The
kernel should clean that out after some time (like 120s or some such),
no?
-- Leif
