Hotfix: FIX: A Service Broker endpoint stops passing messages in a database mirroring session of SQL Server 2005

SYMPTOMS
In a database mirroring session of Microsoft SQL Server 2005, a Service Broker endpoint stops passing messages from the initiating service to the target service. This problem occurs periodically and with increasing frequency.

When this problem occurs, a minidump file is generated. Additionally, the following error messages are repeatedly logged in the SQL Server 2005 error log:
Date Time SPID The mirror route is not operational. 'TCP://plpossrv135:4027' is acting as 'Unknown' []. 'tcp://slpossrv135:4027' is acting as 'Unknown' [].
Date Time SPID The mirror route is operational, but only connected to principal. 'TCP://plpossrv048:4027' is acting as 'Principal' []. 'tcp://slpossrv048:4027' is acting as 'Unknown' [].
Date Time Backup Log was backed up. Database: ShvaWebHO, creation date(time): 2006/07/17(23:01:56), first LSN: 50098:8649:37, last LSN: 50136:18614:1, number of dump devices: 2, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'VDI_0F67AA24-5C91-47D6-B048-7662275C1E35_0', 'VDI_0F67AA24-5C91-47D6-B048-7662275C1E35_1'}). This is an informational message only. No user action is required.
Date Time SPID Timeout occurred while waiting for latch: class 'SERVICE_BROKER_TRANSMISSION_WORK', id 0000000082EA40E0, type 4, Task 0x0000000004ACC718 : 0, waittime 300, flags 0xa, owning task 0x00000000052F9978. Continuing to wait.
Date Time SPID Using 'dbghelp.dll' version '4.0.5'
Date Time SPID **Dump thread - spid = 104, PSS = 0x0000000089DCEB40, EC = 0x0000000089DCEB50
Date Time SPID ***Stack Dump being sent to R:\Microsoft SQL Server\MSSQL.6\MSSQL\LOG\SQLDump0011.txt
Date Time SPID * *******************************************************************************
Date Time SPID *
Date Time SPID * BEGIN STACK DUMP:
Date Time SPID * 06/26/07 13:16:51 spid 104
Date Time SPID *
Date Time SPID * Latch timeout
Date Time SPID *
Date Time SPID *
Date Time SPID * *******************************************************************************
Date Time SPID * -------------------------------------------------------------------------------
Date Time SPID * Short Stack Dump
Date Time SPID Stack Signature for the dump is 0x0000000156139452
Date Time SPID Timeout occurred while waiting for latch: class 'SERVICE_BROKER_TRANSMITTER', id 0000000080283900, type 4, Task 0x0000000003C74EF8 : 0, waittime 300, flags 0x1008, owning task 0x0000000000000000. Continuing to wait.
Date Time SPID External dump process return code 0x20000001.Date

RESOLUTION
Cumulative update information
The fix for this issue was first released as a hotfix and is also available in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
941450 (http://support.microsoft.com/kb/941450/ ) Cumulative update package 4 for SQL Server 2005 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. We recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 937137 (http://support.microsoft.com/kb/937137/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.