Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#64 NsQueueConn failure for one queue effects all queues

Bug
closed-wont-fix
nobody
5
2013-05-11
2006-07-24
Stephen
No

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.

Discussion

  • Logged In: YES
    user_id=95086

    It is myself who wrote that comment when I was looking at that
    code some months ago, as this was not very clear. I recall talking
    to Vlad about that but I can't recall what was the outcome!

     
  • Stephen
    Stephen
    2006-12-01

    • labels: --> NaviServer - libnsd, libnsthread, nsd
     
  • Stephen
    Stephen
    2006-12-01

    • milestone: 469714 --> 473033
     
  • Stephen
    Stephen
    2006-12-01

    • milestone: 473033 --> Bug
     
  • gustafn
    gustafn
    2013-05-11

    • labels: NaviServer - libnsd, libnsthread, nsd --> NaviServer - libnsd, libnsthread, nsd
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,4 +1,3 @@
    -
     A comment in nsd/driver.c states:
    
     /\*
    
    • status: open --> closed-wont-fix
     
  • gustafn
    gustafn
    2013-05-11

    the new driver is quite different, try to locate fix the original bug is quite impossible.