[racket] web server stopped responding to TCP connections

Just checking my mail now after the holiday... I've thought that I've
seen this before, but the problem has been something else in each
case. In one case I actually had something like an infinite loop in my
program that starved the CPU of the accept() thread and so there were
TCP-level timeouts on the clients. I'm very interested in a
reproducible error. One suggestion would be to use dispatch-server
directly without any HTTP work and see if you can get it to happen at
that level.

Jay

On Tue, Dec 30, 2014 at 1:28 PM, Tony Garnock-Jones <tonyg at ccs.neu.edu> wrote:
> On 12/29/2014 08:25 PM, George Neuner wrote:
>>> Are you using Racket's SSL support, or is it http-only?
>> It's HTTP only.  My application hides behind Apache on the same host so
>> it doesn't need SSL.
>
> That's good to know -- so *if* it's the same fault we're both seeing,
> then it's not limited to just the SSL code, but is related to the
> web-server or even to TCP support generally.
>
>>> Are you on Linux, a different Unixalike, or Windows?
>> Yes.  8-)
>
> Excellent. So again, *if* it's the same fault, it's both (64-bit) Linux
> and Windows 7.
>
> Thanks!
>
> Tony
> ____________________
>   Racket Users list:
>   http://lists.racket-lang.org/users



-- 
Jay McCarthy
http://jeapostrophe.github.io

           "Wherefore, be not weary in well-doing,
      for ye are laying the foundation of a great work.
And out of small things proceedeth that which is great."
                          - D&C 64:33