locked
How make sure all connections are closed when user disconnects? RRS feed

  • Question

  • Hi!

    If a user hangs up when the mss workflow app is busy doing an extensive database lookup (or waiting for a connection from the connection pool), is it possible to cancel the request?

    I have error handling in the data access layer that closes connections but if an error occurs on a higher level I would like to free resources as well. When load is high I do not want users who hang up because the system doesn't respond fast enough to cause even greater load.

     

    Is this possible? Do I have to have my own connection pool to be able to see which are used (dreaded thought) or keep a reference to the current connections in the workflow so that they can be closed? I suspect doing this might give me even greater problems...

     

    Thanks for your input!

    Tuesday, May 29, 2007 6:33 AM

Answers

  • The answer to your question lies in whatever APIs you are using for your database lookup.  I suggest reading the documentation for those APIs.  You can invoke the cancel from the call disconnected fault handler on your workflow. 

    Wednesday, May 30, 2007 8:54 AM