fastify.close() takes over a minute if one GET request is made

[AmosSzust]

I created the simplest server using fastify with one get('/') route. On SIGTERM/SIGINT I do fastify.close(). To close the server I press the red rectangle (webstorm).

If no requests were made, closing is done immediately. If I do one simple GET request that is completed successfully, it takes over a minute until fastify.close() reaches its callback and even then, it looks like a timeout/force and not because of a graceful shutdown(?).

I tried keepAliveTimeout but it didn't change anything.

const fastify = Fastify({
  logger: true,
  keepAliveTimeout: 10000,
});

Am I missing something?

[jsumners]

• https://fastify.dev/docs/latest/Reference/Server#keepalivetimeout
• https://fastify.dev/docs/latest/Reference/Server#forcecloseconnections

[AmosSzust]

The number of milliseconds of inactivity a server needs to wait for additional incoming data, after it has finished writing the last response, before a socket will be destroyed. If the server receives new data before the keep-alive timeout has fired, it will reset the regular inactivity timeout, i.e., server.timeout.

I thought this was the problem so I set keepAliveTimeout: 10000 but it didn't change anything.

When set to true, upon close the server will iterate the current persistent connections and destroy their sockets.

I don't want to foce closing connections, I want it to wait for them to close and then close the server itself. Not sure why and which connection remains open that prevents the server from closing.

[jsumners]

Your client is establishing a keep alive connection. You have to terminate the client's connection on either end.

[AmosSzust]

It's a browser's (Edge) url, a simple localhost:8090 , does the browser establish a keep alive connection?

[jsumners]

Yes.

[AmosSzust]

grrr... I now tried with a rest client extension and indeed it was closed immediately even after requesting. Thanks,