From: SourceForge.net <no...@so...> - 2006-07-24 20:43:53
|
Bugs item #1527964, was opened at 2006-07-24 14:43 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=719006&aid=1527964&group_id=130646 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Current Status: Open Resolution: None Priority: 5 Submitted By: Stephen Deasey (sdeasey) Assigned to: Nobody/Anonymous (nobody) Summary: NsQueueConn failure for one queue effects all queues Initial Comment: A comment in nsd/driver.c states: /* * Hint: NsQueueConn may fail to queue a certain * socket to the designated connection queue. * In such case, ALL ready sockets will be put on * the waiting list until the next interation, * regardless of which connection queue they are * to be queued. */ This may be a problem for quick error reponses (Server Busy, Error etc.), whose connection now needs to be kept open, consuming resources, when an empty queue exists which could service the request. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=719006&aid=1527964&group_id=130646 |