none
Closed status sys.conversation_endpoints not being automatically purged RRS feed

  • Question

  • Is there any reason why conversation_endpoints in a Closed status are not automatically purged?  Both the initiator and receiver are issuing END CONVERSATION requests resulting in a Closed status.  However, we have millions of closed endpoints never getting purged from sys.conversation_endpoints.
    Monday, March 17, 2014 7:47 PM

All replies

  • Hi Simmon,

    Thanks for your question. I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. 

    Thank you for your understanding and support.

    If you have any feedback on our support, please click here.

    Regards,


    Elvis Long
    TechNet Community Support

    Wednesday, March 19, 2014 1:17 PM
    Moderator
  • Is the datetime in security_timestamp field in the future or in the past? Note that the time is UTC time. 
    The correct behavior is for the target endpoint to be deleted after the security_timestamp has expired, which is usually in 30 minutes after the first reply from target to the initiator was acknowledged. In the cases when the target never sends any reply to the initiator (including an EndDialog reply) then it is known that the target will be leaked, but this is an incorrect message exchange patter (fire-and-forget) not only because of this problem but for other reasons too, see Fire and Forget: Good for the military, but not for Service Broker conversations
    However in the same instance and same database even the fire-and-forget scenario should work and not leave the target endpoint leaked. If you have a consistent repro scenario for a case when the target endpoint security_timestamp is initialized but the endpoint is not deleted after this timestamp has expired I suggest you contact the product team, perhaps using Connect: SQL Server 
    Thursday, March 27, 2014 1:06 PM