[Mono-bugs] [Bug 677539] New: SocketAsyncEventArgs reuse causes errors, BytesTransferred is not set back to 0
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Mon Mar 7 16:10:15 EST 2011
https://bugzilla.novell.com/show_bug.cgi?id=677539
https://bugzilla.novell.com/show_bug.cgi?id=677539#c0
Summary: SocketAsyncEventArgs reuse causes errors,
BytesTransferred is not set back to 0
Classification: Mono
Product: Mono: Class Libraries
Version: 2.10.x
Platform: All
OS/Version: RHEL 5
Status: NEW
Severity: Critical
Priority: P5 - None
Component: System
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: wwaxpoetic at yahoo.com
QAContact: mono-bugs at lists.ximian.com
CC: gonzalo at novell.com, tobias.peciva at kaseya.com
Depends on: 644428
Found By: Development
Blocker: No
I’m implementing a socket server by using code from this link:
http://www.codeproject.com/KB/IP/socketasynceventargs.aspx
This code implements a pool of socketaynceventargs which is for reusing SAEA
objects.
When a socket is disconnected SAEA object is pushed back to the pool, then if
needed it pulls that same socketasynceventargs.
When I was using version 2.8.2 that code worked as expected. I recently updated
to 2.10.1 and now it’s broken.
The same code work well in .NET 4.0 Client Profile.
I investigated the problem and saw that closing AcceptSocket which is bound to
SAEA object doesn’t set BytesTransferred to 0
in version 2.10.1 but that’s not the case with 2.8.2
Ufuk
--
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