(Republishing, or using this info in a commercial product/website, is prohibited without permission. All other uses are permitted. If in doubt, please ask.)
Paraphrased from the old Service Broker team blog: This wait type is when a thread requires exclusive access to a connection endpoint. This occurs whenever a connection is established to the endpoint and whenever the DMV sys.dm_broker_connections is executed (or the DMV sys.dm_db_mirroring_connections, as database mirroring uses Service Broker as its underlying transport mechanism).
(Books Online description: “Occurs when there is contention to access the state of a Service Broker connection endpoint. Access to the state for changes is serialized.”)
Questions/comments on this wait type? Click here to send Paul an email, especially if you have any information to add to this topic.
Added in SQL Server version:
Removed in SQL Server version:
Extended Events wait_type value:
The map_key value in sys.dm_xe_map_values is 285 in 2008 and 2008 R2, 291 in 2012, and 298 in 2014 RTM. After 2014 RTM, you must check the DMV to get the latest value as some map_key values have changed in later builds.
I have not seen this wait type be a noticeable contention point.
If the number of waits for this wait type is increasing rapidly, it could be that there are a large number of connections being made, or there is repeated inactivity over a connection, as inactive connections will be removed every 90 seconds or so.
Known occurrences in SQL Server (list number matches call stack list):
Abbreviated call stacks (list number matches known occurrences list):