This documentation is archived and is not being maintained.

ServiceBehaviorAttribute.ReleaseServiceInstanceOnTransactionComplete Property

Gets or sets a value that specifies whether the service object is released when the current transaction completes.

Namespace: System.ServiceModel
Assembly: System.ServiceModel (in system.servicemodel.dll)

public bool ReleaseServiceInstanceOnTransactionComplete { get; set; }
/** @property */
public boolean get_ReleaseServiceInstanceOnTransactionComplete ()

/** @property */
public void set_ReleaseServiceInstanceOnTransactionComplete (boolean value)

public function get ReleaseServiceInstanceOnTransactionComplete () : boolean

public function set ReleaseServiceInstanceOnTransactionComplete (value : boolean)

Not applicable.

Property Value

true if the service object is to be released; otherwise, false. The default is true.

Note that you must explicitly set ReleaseServiceInstanceOnTransactionComplete to false if there is an operation with OperationBehaviorAttribute.TransactionScopeRequired set to true and you set ConcurrencyMode to Reentrant. Otherwise a validation exception is thrown because the default value of ReleaseServiceInstanceOnTransactionComplete is true.

In addition, it is important to realize that if the service is created by passing a service object to the System.ServiceModel.ServiceHost(Object,Uri[]) constructor, the value of this property is treated as if it were false.

The following code example sets the transaction isolation level to ReadCommitted, disables support for concurrent transactions, requires a flowed transaction from the operation call, and commits the transaction on the service automatically if no unhandled exception occurs.

using System;
using System.ServiceModel;
using System.Transactions;

namespace Microsoft.WCF.Documentation
  public interface IBehaviorService
    string TxWork(string message);

  // Note: To use the TransactionIsolationLevel property, you 
  // must add a reference to the System.Transactions.dll assembly.
  /* The following service implementation:
   *   -- Processes messages on one thread at a time
   *   -- Creates one service object per session
   *   -- Does not release the service object when the transaction commits
   *   -- The isolation level is read committed.
  public class BehaviorService : IBehaviorService, IDisposable
    Guid myID;

    public BehaviorService()
      myID = Guid.NewGuid();
        "Object "
        + myID.ToString()
        + " created.");

     * The following operation-level behaviors are specified:
     *   -- Always executes under a transaction scope.
     *   -- The transaction scope is completed when the operation terminates
     *       without an unhandled exception.
      TransactionAutoComplete = true,
      TransactionScopeRequired = true
    public string TxWork(string message)
      // Do some transactable work.
      Console.WriteLine("TxWork called with: " + message);
      // Display transaction information.

      TransactionInformation info = Transaction.Current.TransactionInformation;
      Console.WriteLine("The distributed tx ID: {0}.", info.DistributedIdentifier);
      Console.WriteLine("The tx status: {0}.", info.Status);
      return String.Format("Hello. This was object {0}.",myID.ToString()) ;

    public void Dispose()
        "Service "
        + myID.ToString()
        + " is being recycled."

The underlying binding must support flowed transactions for the following code example to execute properly. To support flowed transactions using the WSHttpBinding, for example, set the TransactionFlow property to true in code or in an application configuration file. The following code example shows a configuration file for the preceding sample.

            <add baseAddress="http://localhost:8080/BehaviorService"/>
            <add baseAddress="net.tcp://localhost:8081/BehaviorService"/>
            This example code uses the WSHttpBinding to support transactions using the 
            WS-AtomicTransactions (WS-AT) protocol. WSHttpBinding is configured to use the  
            protocol, but the protocol is not enabled on some computers. Use the xws_reg -wsat+ 
            command to enable the WS-AtomicTransactions protocol in the MSDTC service.          
        <behavior name="mex">
          <serviceMetadata httpGetEnabled="true"/>
    <!-- binding configuration - configures a WSHttpBinding to require transaction flow -->
        <binding name="wsHttpBindingWithTXFlow" transactionFlow="true" />
        <binding name="netTcpBindingWithTXFlow" transactionFlow="true" />


Windows 98, Windows Server 2000 SP4, Windows CE, Windows Millennium Edition, Windows Mobile for Pocket PC, Windows Mobile for Smartphone, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition

The Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.

.NET Framework

Supported in: 3.0