Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Transactions commit asynchronously and after the fact. You can't react to a failure of the transaction to commit because of a problem at the resource manager level.</p> <p>As you pointed out, you can deal with exceptions that occur in your activities. If you look at the tracking records for your workflow my guess is that you would see the TryCatch activity is closed prior to the transaction abort. </p> <p>Many years ago when I was a program manager in the COM+ team I studied this issue because often people want a transactional component (or workflow) as in this case to be able to react to a transaction abort.</p> <p>The async nature of the resolution of the transaction means that you simply cannot react to it in the component itself. The solution is to react in the caller which can then take some action.</p> <p>The design assumption is that once a transaction has aborted, nothing about state aqcuired in the transaction can be safely used - it will all be discarded because the transaction is aborted.</p>
    singulars
    1. This table or related slice is empty.
    1. POException escapes from workflow despite TryCatch activity
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRon Jacobs
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POException escapes from workflow despite TryCatch activity
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COInteresting. I'm not convinced this is the actual problem, however. I actually do not see my TryCatch activity closing before the transaction abort. However, I took another look at what happens when the TransactionScope activity completes. It appears to queue a `CompleteTransactionWorkItem`. This indicates that something asynchronous is going on. However, this must also mean that at some point in time, the workflow thread and the transaction thread join to give me back the stacktrace I posted. I do not see this happening anywhere (I can't even find another thread dequeueing work items).
      singulars
      1. PO
      1. USRonald Wildenberg
    2. COActually what happens is that once the transaction fails the workflow terminates immediately (this is why the try/catch does not close). If you were able to invoke code in the workflow when the transaction is aborting you might inadvertantly do something with state created under the transaction that is failing. This violates the isolation semantic of the transaction so it is not allowed.
      singulars
      1. PO
      1. USRon Jacobs
    3. COOk, I understand. But it seems a little counter-intuitive to have a `TryCatch` that doesn't actually catch something I expected to be caught. So when using a `TransactionScope` inside a workflow, you have to carefully consider what you want the behavior to be when the transaction aborts. I should probably just go check out some more Endpoint.tv shows :)
      singulars
      1. PO
      1. USRonald Wildenberg
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload