Post reply

Service Broker Disconnected Conversations

  • June 20, 2019 at 12:00 am

    #3648483

    Comments posted to this topic are about the item Service Broker Disconnected Conversations

  • June 20, 2019 at 4:51 am

    #3655582

    That is interesting, thanks for the question.

    Have never used a "fire & forget" pattern myself...

    ____________________________________________
    Space, the final frontier? not any more...
    All limits henceforth are self-imposed.
    “libera tute vulgaris ex”

  • June 21, 2019 at 1:50 pm

    #3656164

    That's good to know,

    As per me END CONVERSATION related option should also be correct as it will also limit the number of inactive connection.

    Please explain on is this a valid consideration ?

     

  • June 21, 2019 at 1:59 pm

    #3656166

    The recommended pattern in any conversation is:

    1. Target service ends conversation.
    2. Initiator service receives "End Conversation" message and responds by ending the conversation on its end.

    In cases where the initiator can't reasonably respond to the "End Conversation" message, the simplest solution is to enable a queue activation stored procedure that ends the conversation on its behalf.

    • This reply was modified 5 years, 5 months ago by  mkdm.

  • June 21, 2019 at 2:01 pm

    #3656170

    Stewart "Arturius" Campbell wrote:

    That is interesting, thanks for the question. Have never used a "fire & forget" pattern myself...

    That's a good thing. 🙂

    • This reply was modified 5 years, 5 months ago by  mkdm.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply