Keep alive connections

By default, the NestJS HTTP adapters wait until responses have finished before closing the application. Sometimes this behavior is unwanted or unexpected: some requests use Connection: Keep-Alive headers and keep their connections open for a long time.

If you want your application to always exit without waiting for these connections to end, enable the forceCloseConnections option when creating your NestJS application.

Hint Most users don't need this option. The typical symptom that you do is an application that doesn't exit when you expect it to, usually with app.enableShutdownHooks() enabled, and most often during development when running with --watch.

Usage#

In your main.ts file, enable the option when creating your NestJS application:

import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module.js';

async function bootstrap() {
  const app = await NestFactory.create(AppModule, {
    forceCloseConnections: true,
  });
  await app.listen(process.env.PORT ?? 3000);
}

await bootstrap();

Note The forceCloseConnections application option is implemented by the Express adapter (@nestjs/platform-express). With Fastify, pass Fastify's own forceCloseConnections server option to the FastifyAdapter constructor instead.