-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deno hangs after a while, serving a static file over HTTPS #10296
Comments
Is it possible that the EC2 instance is spinning down? You can set the minimum instances to 0, so you may occasionally experience a cold start. I'd start by adding logging to see if the request is making it to the server. |
I have an SSH session open on the server and it remains responsive at all times while that happens.
As shown in my code, Deno outputs all requests it receives. When it starts hanging, it stops outputting anything. Where else would you suggest I look? |
@AaronO I'm not entirely sure it's the same issue. The static files I use are only 6 kilobytes. Moreover, I've been running version 1.7.0 and I still get the same error, albeit perhaps less frequently. In any case, I didn't realise it when I posted this issue, but am I not supposed to run Deno's newly released native API anyway? |
…ite half" using tokio::io::split() to allow concurrent Conn#read() and Conn#write() calls without one blocking the other. However, this introduced a bug: outgoing data gets discarded when the TLS stream is gracefully closed, because the read half is closed too early, before all TLS control data has been received. Fixes: denoland#9692 Fixes: denoland#10049 Fixes: denoland#10296 Fixes: denoland/std#750
denoland#10146) In denoland#9118, TLS streams were split into a "read half" and a "write half" using tokio::io::split() to allow concurrent Conn#read() and Conn#write() calls without one blocking the other. However, this introduced a bug: outgoing data gets discarded when the TLS stream is gracefully closed, because the read half is closed too early, before all TLS control data has been received. Fixes: denoland#9692 Fixes: denoland#10049 Fixes: denoland#10296 Fixes: denoland/std#750
|
I've set up a rudimentary server on AWS EC2 (Debian Linux) running Deno 1.9.1 with an SSL certificate from Let's Encrypt. It simply serves a static HTML file when dealing with a GET request for "/", and returns a 404 for all other requests.
It works fine for a while, and then starts hanging on all requests after a seemingly random amount of time. The code is the following:
After the server starts hanging, curl outputs the following (and hangs as well):
Am I doing something wrong? I'm starting a big project based on Deno and this is blocking.
The text was updated successfully, but these errors were encountered: