More on using a TransactionScopeActivity within a ReceiveActivity

A bit more about using TransactionScopeActivity within a ReceiveActivity

WF Community Bloggers — Tue, 16 Sep 2008 10:14:01 GMT

Part 1 part 2 Part 3 Part 4 You may recall my previous posts about using the TransactionScopeActivity

Using a TransactionScopeActivity within a ReceiveActivity in a state machine workflow - The Problem Solver

Tue, 16 Sep 2008 10:10:40 GMT

Pingback from Using a TransactionScopeActivity within a ReceiveActivity in a state machine workflow - The Problem Solver

More on using a TransactionScopeActivity within a ReceiveActivity - The Problem Solver

Tue, 16 Sep 2008 10:09:20 GMT

Pingback from More on using a TransactionScopeActivity within a ReceiveActivity - The Problem Solver

A bit more about using TransactionScopeActivity within a ReceiveActivity

The Problem Solver — Tue, 16 Sep 2008 10:06:05 GMT

You may recall my previous posts about using the TransactionScopeActivity within a ReceiveActivity and

re: More on using a TransactionScopeActivity within a ReceiveActivity

Kenny Wolf — Mon, 15 Sep 2008 00:07:52 GMT

FWIW, the documentation also mentions this (though it isn't particularly helpful since you don't get viable alternatives in 3.5)

msdn.microsoft.com/.../system.workflow.activities.receiveactivity.aspx

"To ensure that persistence performs properly and does not persist transient messages, make sure that child activities of the ReceiveActivity do not persist by themselves. This can occur if the child activities go idle when a persistence provider was created with UnloadOnIdle set to true, for instance. "

It is an unfortunate limitation, and one we plan on addressing in the next release.

re: More on using a TransactionScopeActivity within a ReceiveActivity

Kenny Wolf — Sun, 14 Sep 2008 23:55:01 GMT

Unfortunately this is not supported in 3.5 and you hit numerous issues if you try (as you've experienced). RecieveMessage in 3.5 was authored as a non-persistable activity (the data it receives is not necessarily persistence-friendly), so either going idle or hitting a persist point (through transactions or [PersistOnClose]) will cause ReceiveMessage all sorts of problems. Life gets better in 4.0 and I'll be able to provide those details after PDC (late October).