netmsmqbinding - Long running WCF MSMQ Processing -


i reading programming wcf services 3rd ed. juval lowy. in chapter "queued services" covers netmsmqbinding, on page 473, says "... should keep service's processing of queued call relatively short, or risk aborting playback transaction. important observation here is wrong equate queued calls lengthy asynchronous calls."

1) short call? 2) best practice long running operations; send send them off threadpool?

this article ran same problem in practice: wcf & msmq & transactionscope long process

i have looked , looked, , cannot find best practices regarding matter on internet.

3) rule apply if have no transaction?

1) default short process transaction takes less 10 minutes (default transaction timeout) 2) can be, if lose transactional behavior (if server goes down message lost) 3) yes. default transaction scope has default timeout abort transaction.

the news can override timeout on machine.config file: http://blogs.inkeysolutions.com/2012/01/managing-timeouts-while-using.html


Comments

Popular posts from this blog

css - Which browser returns the correct result for getBoundingClientRect of an SVG element? -

gcc - Calling fftR4() in c from assembly -

.htaccess - Matching full URL in RewriteCond -