Part of the SQL Server Wait Types Library.
Related deep dive: SOS_SCHEDULER_YIELD Wait Type.
BROKER_TASK_STOP is recorded when a Service Broker internal task handler waits (up to ten seconds at a time) to shut itself down because there are no Broker tasks, message transmission, receipt, or other asynchronous network operations, for it to handle. The shutdown check is serialised, hence a wait type for it.
Its accumulation follows a predictable clock: Broker schedules a background cleanup every five seconds when in use, so this wait grows steadily whether Broker is busy or idle.
Is It a Problem?
No; it is a benign lifecycle wait for Broker’s task handler pool and belongs on the filter list. Its steady growth (five seconds per five seconds when Broker is used, ten-second increments otherwise) is timer arithmetic, not workload signal.
Broker health questions route elsewhere, as ever: sys.transmission_queue for delivery, activation procedure errors in the error log, conversation counts for leaks.
Common Causes
- Service Broker’s task handler lifecycle running its shutdown checks on schedule.
- Instances with Broker enabled databases (including msdb, which uses Broker internally).
What To Do
- Filter it out of wait analysis.
- Nothing else; the handler pool manages itself.
How To See It
Rank waits with Get-WaitStatistics, where it is filtered as Broker background noise.
Leave a Reply