HostWeb Forums » Microsoft Databases » microsoft.public.sqlserver.servicebroker » RE: sys.conversation_endpoints
Topic: RE: sys.conversation_endpoints
Hello Al,
You need to make sure you end the conversation on both ends.
The conversation end points stick around to make sure the same messages can't
be resent.
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> OK, if we specify a "lifetime" of the conversation, and end (close)
> the conversation within the lifetime, then the
> sys.conversation_endpoints entry is removed about 30 mintues after the
> conversation was due to expire
>
> "Al" wrote:
>
>> First question, at what point are entires removed from the
>> sys.conversation_endpoints system view?
>> As there is a status of CLOSED, I'm assuming that it doesn't occur
>> when the
>> converation has been ended by both sides of the dialogue, otherwise
>> when
>> would an entry go into that status?
>> The second question (and problem), is that we have a situation in
>> which the target sys.conversation_endpoints view is just growing in
>> size, and all the entries are in the CLOSED state (processing is for
>> a single message in a dialogue, and processed immediately). By the
>> initiators sys.conversation_endpoints is empty. Is this normal
>> behaviour? I should also say that in this enviroment we have seperate
>> SQL Servers, within the same Domain, each running under a different
>> domain account.
>>
>> Any answers / help greatly appreciated.
>>
Replies below ↓