[Mono-bugs] [Bug 384534] New: timeout for tcpchannel doesn't work
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Mon Apr 28 17:21:09 EDT 2008
https://bugzilla.novell.com/show_bug.cgi?id=384534
Summary: timeout for tcpchannel doesn't work
Product: Mono: Runtime
Version: SVN
Platform: i686
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: remoting
AssignedTo: lluis at novell.com
ReportedBy: knuckles at gmail.com
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Created an attachment (id=210975)
--> (https://bugzilla.novell.com/attachment.cgi?id=210975)
Test Case
When configuring a tcpchannel with:
System.Collections.IDictionary props = new System.Collections.Hashtable();
props["timeout"] = 1000;
TcpChannel channel = new TcpChannel(props, null, provider);
ChannelServices.RegisterChannel(channel,false);
and then doing a remote invocation, after 1s it doesn't time out (it never
seems to time out).
On ms .net it works fine.
See attached examples, compile with:
gmcs Server.cs CommonTypes.cs -pkg:dotnet
and
gmcs Client.cs CommonTypes.cs -pkg:dotnet
When it runs this is supposed to happen:
C:\>Client.exe
[after 1s]
Could not locate server
Server:
C:\>Server.exe
<enter> para sair...
...................................................................................................
...................................................................................................
.............................................
On mono the client just sits there, never causing the exception that gives that
"could not locate server" error.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the mono-bugs
mailing list