Transaction handling

This topic has 2 replies, 1 voice, and was last updated 4 years ago by biztalkgurus.

Viewing 2 reply threads

Author

Posts
- October 7, 2005 at 5:55 AM #12035
  community-content
  i need some kind help currently i am working on biztalk server 2004 i have an issue related to transaction handling in following scenario.
  i have an orchestration that is doing something in an atomic transaction,
  then it calls a .net component that do something in his own transaction and then commit it and problem starts from here, if later on i do roll back
  then the work done by .net component does not roll baked.
  i cant avoid .net components suggest me some solution.
  
  thnx in advance
  Farukh.
- October 7, 2005 at 6:32 AM #12034
  community-content
  Hello.
  
  We ran into something like that in the past. If I remember correctly, we ended up changing the transaction type on the .net component to participate in the Atomic transaction that was created inside the Orchestation rather then creating a new one inside the Atomic Transaction.
  
  These two blog posts might help you:
  http://dallas.sark.com/SarkBlog/mholdorf/archive/2004/10/12/430.aspx
  http://dallas.sark.com/SarkBlog/mholdorf/archive/2004/12/14/550.aspx
  
  Hope this helps.
- November 14, 2020 at 12:20 PM #50070
  biztalkgurus
  Fire Horse by Sharon Siamon • 9781552854570
Author

Posts

Viewing 2 reply threads

The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.