Bug 932 – TCP connection limit does not work and isn't needed anyway

Bug 932 - TCP connection limit does not work and isn't needed anyway

Summary:

TCP connection limit does not work and isn't needed anyway

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Audio
Version:	unspecified
Platform:	PC All

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Blackketter Dean

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-03-02 16:04 UTC by Sean Adams
Modified:	2008-08-18 10:53 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Sean Adams 2005-03-02 16:04:04 UTC

The server reaches a deadlock if the TCP connection limit is ever reached. This
can happen under not-too-bizarre conditions, eg browser's keepalive limit
increased. Resets coming in on old connections are not handled, so the excess
connections are never cleaned up.

This features should be either:

a) removed

or 

b) fixed, and the limit increased to 100 or more

Comment 1 Blackketter Dean 2005-03-11 17:12:26 UTC

I will remove.