Databases
StackOverflow2013
Postsdbo
POService Broker : Sys.Conversation_endpoints filling up with CO/CONVERSING messages when using With Cleanup
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POService Broker : Sys.Conversation_endpoints filling up with CO/CONVERSING messages when using With Cleanup
    primarykey
    data
    text
    <p>We recently identified a problem with one of our databases where as a result of a 'fire &amp; forget' setup (i.e: conversations being closed immediately after sending), our sys.conversation_endpoints table was filling up with DI/DISCONNECTED_INBOUND messages. This eventually spilled over into the tempDB, causing it to grow enormously and eat up precious disk space. We eventually resolved this issue by commenting out the line </p> <p><code>END CONVERSATION @handle WITH CLEANUP</code></p> <p>in our sending SP and closing the conversations in our receiving SP using the same code,</p> <p><code>END CONVERSATION @handle WITH CLEANUP</code></p> <p>However, we now have a new issue. Since moving servers (and migrating from SQL Server 2005 to SQL Server 2008) we've recently discovered that sys.conversation_endpoints is now filling up with CO/CONVERSING messages, indicating that the conversations are not being closed. The receiving SP is closing them, or at least is running the command to do so, so I don't understand where these messages are coming from. </p> <p>I've tried going back to ending the conversation at the point of send, but it has no effect. Is it wrong to end conversations on the receiving end using <code>WITH CLEANUP</code>? Or is there some other problem? </p> <p>This <a href="http://itknowledgeexchange.techtarget.com/sql-server/service-broker-may-not-remove-messages-after-processing/" rel="nofollow noreferrer">post on techtarget</a> seems to suggest its a bug, and that running a job to cleanup the leftovers is the only solution...</p> <p>UPDATE: Pawel pointed out below that I should be avoiding the Fire &amp; Forget Pattern, and I've added an activated SP to the initiator queue to end any conversations. However, sys.conversation_endpoints is STILL filling up, this time with CD/CLOSED messages. Here's the structure of my queues</p> <p>Send_SP: </p> <pre><code>DECLARE @h UNIQUEIDENTIFIER BEGIN DIALOG CONVERSATION @h FROM SERVICE 'InitiatorQueue' TO SERVICE 'TargetQueue' ON CONTRACT 'MyContract' WITH ENCRYPTION = OFF; SEND ON CONVERSATION @h MESSAGE TYPE 'MyMessage' (@msg) </code></pre> <p>Receive_SP (Activated SP on TargetQueue)</p> <pre><code>DECLARE @type SYSNAME, @h UNIQUEIDENTIFIER, @msg XML; DECLARE @target TABLE ( [message_type_name] SYSNAME, [message_body] VARBINARY(MAX), [conversation_handle] UNIQUEIDENTIFIER ) WHILE(1=1) BEGIN TRANSACTION WAITFOR(RECEIVE TOP (1000) [message_type_name],[message_body],[conversation_handle] FROM TargetQueue INTO @target), TIMEOUT 2000 IF(@@rowcount!=0) BEGIN WHILE((SELECT count(*) FROM @target) &gt; 0) BEGIN SELECT TOP (1) @type = [message_type_name], @msg = [message_body], @h = [conversation_handle] FROM @target; // Handle Message Here END CONVERSATION @h; DELETE TOP (1) FROM @target; END END COMMIT TRANSACTION; </code></pre> <p>End_SP (Activated SP on InitiatorQueue)</p> <pre><code>DECLARE @type SYSNAME, @h UNIQUEIDENTIFIER, @msg XML; DECLARE @init TABLE ( [message_type_name] SYSNAME, [message_body] VARBINARY(MAX), [conversation_handle] UNIQUEIDENTIFIER ) WHILE(1=1) BEGIN TRANSACTION WAITFOR(RECEIVE TOP (1000) [message_type_name],[message_body],[conversation_handle] FROM InitiatorQueue INTO @init), TIMEOUT 2000 IF(@@rowcount!=0) BEGIN WHILE((SELECT count(*) FROM @init) &gt; 0) BEGIN SELECT TOP (1) @type = [message_type_name], @msg = [message_body], @h = [conversation_handle] FROM @init; END CONVERSATION @h; DELETE TOP (1) FROM @init; END END COMMIT TRANSACTION; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USroryok
    1. USroryok
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POService Broker : Sys.Conversation_endpoints filling up with CO/CONVERSING messages when using With Cleanup
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POService Broker : Sys.Conversation_endpoints filling up with CO/CONVERSING messages when using With Cleanup
      1. USStephen Turner
      1. VTFavorite
    3. VO
      singulars
      1. POService Broker : Sys.Conversation_endpoints filling up with CO/CONVERSING messages when using With Cleanup
      1. USmr.sverrir
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload