[Mono-bugs] [Bug 691486] New: TcpClient.BeginConnect doesn't call callback
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Tue May 3 12:21:04 EDT 2011
https://bugzilla.novell.com/show_bug.cgi?id=691486
https://bugzilla.novell.com/show_bug.cgi?id=691486#c0
Summary: TcpClient.BeginConnect doesn't call callback
Classification: Mono
Product: MonoDroid
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Class Libraries
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: rich at ase-systems.com
QAContact: mono-bugs at lists.ximian.com
Found By: Development
Blocker: No
Created an attachment (id=427799)
--> (http://bugzilla.novell.com/attachment.cgi?id=427799)
MonoDroid & Windows .Net projects.
Description of Problem:
After successful connection to server, the asynchronous TcpClient.BeginConnect
does not call the callback or sometimes aborts. It may work the first call, but
never the second. The synchronous, TcpClient.Connect works fine.
Steps to reproduce the problem:
1. Call TcpClient.BeginConnect with appropriate parameters.
2. After successfull connection, the callback is not called.
Actual Results:
The callback is either not called or it aborts.
Expected Results:
The callback should be called
How often does this happen?
Sometimes the first call works, but never after that.
Additional Information:
Attached are two projects.
1) A MonoDroid project that demonstrates the behavior.
2) An equivalent Windows .NET projects that demonstrates correct behavior.
The projects contain a server and a client. The server just counts connections.
The client allows for asynchronous and synchronous connections and
disconnections to the specified server. The port used is 20000.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list