A hotfix is available that adds an endpoint behavior that lets services use multiple threads to receive secure messages in the .NET Framework 3.5 SP1

Article translations Article translations
Article ID: 975955 - View products that this article applies to.
Expand all | Collapse all

On This Page

INTRODUCTION

In the .NET Framework 3.5 Service Pack 1 (SP1), you can use only one thread to receive secure messages in a Windows Communication Foundation (WCF) service that uses message security. This hotfix adds the dispatcherSynchronization endpoint behavior that lets you use multiple threads to receive secure messages at the same time. Additionally, the behavior contains the maxPendingReceives property. This property enables you to set the maximum number of threads that receive secure messages at the same time.

MORE INFORMATION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have the .NET Framework 3.5 SP1 installed on one of the following operating systems:
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 SP2

Restart requirement

You do not have to restart the computer after you apply this hotfix if no instance of the .NET Framework is being used.

Hotfix replacement information

This hotfix does not replace other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
For all supported x86-based versions of Windows Vista SP2 and of Windows Server 2008 SP2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Servicemonikersupport.dll3.0.4506.442917,24002-Nov- 200907:54
System.identitymodel.dll3.0.4506.4429434,17602-Nov- 200907:53
System.runtime.serialization.dll3.0.4506.4429970,75202-Nov- 200907:54
System.servicemodel.dll3.0.4506.44295,943,29602-Nov-200907:54

For all supported x64-based versions of Windows Vista SP2 and of Windows Server 2008 SP2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Servicemonikersupport.dll3.0.4506.442919,30402-Nov- 200907:53x64
System.identitymodel.dll3.0.4506.4429393,21602-Nov- 200907:53x64
System.runtime.serialization.dll3.0.4506.4429847,87202-Nov- 200907:53x64
System.servicemodel.dll3.0.4506.44295,279,74402-Nov- 200907:53x64

For all supported Itanium-based versions of Windows Server 2008 SP2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Servicemonikersupport.dll3.0.4506.442933,62402-Nov- 200907:54IA-64
System.identitymodel.dll3.0.4506.4429393,21602-Nov- 200907:53IA-64
System.runtime.serialization.dll3.0.4506.4429847,87202-Nov- 200907:53IA-64
System.servicemodel.dll3.0.4506.44295,279,74402-Nov- 200907:54IA-64

How to add the dispatcherSynchronization endpoint behavior

To add the behavior, follow these steps:
  1. Install the hotfix.
  2. Create a new endpoint behavior. Then, add the behavior to a service endpoint that applies message security to a configuration file. Use a configuration that resembles the following sample configuration to create and then add the behavior:
    <endpointBehaviors>
            <behavior name="ServiceEPBehavior">
              <dispatcherSynchronization maxPendingReceives="x"/>
            </behavior>
    </endpointBehaviors>
    ...
    <services>
          <service name="MicrosoftMyTestService">
           		<endpoint address="http://loocalhost/IService" binding="customBinding"
                      		contract="IService"
                      		behaviorConfiguration="ServiceEPBehavior" bindingConfiguration="MyCustomBinding">
           		</endpoint>
          </service>
    </services>
    
Note The "x" placeholder in the sample configuration represents the maximum number of threads that receive secure messages at the same time.

For more information about the dispatcherSynchronization endpoint behavior in the .NET Framework 4.0, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/system.servicemodel.description.dispatchersynchronizationbehavior(VS.100).aspx

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Properties

Article ID: 975955 - Last Review: October 7, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft .NET Framework 3.5
  • Microsoft .NET Framework 3.5 Service Pack 1
Keywords: 
kbexpertiseadvanced kbsurveynew kbqfe KB975955

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com