Microsoft KB Archive/923614

= FIX: The TCPChannel class does not contain the Timeout property in the .NET Framework 1.1 =

Article ID: 923614

Article Last Modified on 4/9/2007

-

APPLIES TO


 * Microsoft .NET Framework 1.1

-



SYMPTOMS
In the Microsoft .NET Framework 1.1, the TCPChannel class does not contain the Timeout property.

Note By default, the TCPChannel class in the Microsoft .NET Framework 2.0 contains the Timeout property.



Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 1.1 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
You must have Microsoft .NET Framework 1.1 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement
You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any 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.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
The following code sample illustrates how to use the Timeout property.

Code for the client-side of the remoting application
Save the following code example to the Client.cs file. Then, use the C# command-line compiler (Csc.exe) to compile the Client.cs file. using System; using System.Text; using System.Runtime.Remoting.Channels.Tcp; using System.Runtime.Remoting; using System.Runtime.Remoting.Channels; using System.Threading; using System.Collections; namespace RemotingTimeOutTest {   class Program {       static void Main(string[] args) {           try {               IDictionary t = new Hashtable; t.Add(&quot;timeout&quot;,(uint)1); TcpClientChannel clientChannel = new TcpClientChannel(t, null); ChannelServices.RegisterChannel(clientChannel); RemoteServer proxy = (RemoteServer)Activator.GetObject(typeof(RemoteServer), &quot;tcp://localhost:9000/RemoteServer.rem&quot;); proxy.DoIt; }           catch (Exception e)            { Console.WriteLine(&quot;Exception in client&quot; + e); }           Console.Read; }   }

public class RemoteServer : MarshalByRefObject {       public void DoIt {       }    } }

Code for the server-side of the remoting application
Save the following code to the Server.cs file. Then, use the C# command-line compiler to compile the Server.cs file. using System; using System.Text; using System.Runtime.Remoting.Channels.Tcp; using System.Runtime.Remoting; using System.Runtime.Remoting.Channels; using System.Threading; using System.Collections; namespace RemotingTimeOutTest {   class Program {       static void Main(string[] args) {           try {               TcpServerChannel serverChannel = new TcpServerChannel(&quot;tcpserver&quot;, 9000); ChannelServices.RegisterChannel(serverChannel); RemotingConfiguration.RegisterWellKnownServiceType(typeof(RemoteServer), &quot;RemoteServer.rem&quot;, WellKnownObjectMode.SingleCall); Console.WriteLine(&quot;Hit any key to exit&quot;); Console.ReadLine; }           catch (Exception e)            { Console.WriteLine(&quot;Exception in client&quot; + e); }           Console.Read; }   }

public class RemoteServer : MarshalByRefObject {       public void DoIt {           try {               Console.WriteLine(&quot;Server called. Sleeping...&quot;); Thread.Sleep(10000); Console.WriteLine(&quot;Server woke up&quot;); }           catch (Exception e)            { Console.WriteLine(&quot;Exception in server invocation&quot; + e); }       }    } } This hotfix adds the Timeout property to the TcpChannel class. The client receives an exception error message if the following conditions are true:
 * The client side of the remoting application configures the Timeout property.
 * The remoting call duration exceeds the time-out value.

The exception error message contains the following text:

System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

By default, if the value of the Timeout property is less than -1, the time-out is handled as infinity in the .NET Framework 1.1.

Note In the .NET Framework 2.0, if the value of the Timeout property is less than -1, you receive an ArgumentOutOfRangeException exception.

This hotfix affects only synchronous calls. This hotfix does not affect asynchronous calls to the HttpWebRequest class, because time-outs for asynchronous calls to the HttpWebRequest class are not supported. To obtain a time-out for asynchronous calls to the HttpWebRequest class, manually create a timer. Then, cancel the pending asynchronous calls to the HttpWebRequest class when the timer times out.

