Bug #36944 IO error multiple connections (I think)
Submitted: 26 May 2008 3:32 Modified: 15 Jul 2008 2:56
Reporter: Jared S (Silver Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / NET Severity:S3 (Non-critical)
Version:5.2.2 OS:Windows (XP)
Assigned to: CPU Architecture:Any
Tags: writing to stream failed

[26 May 2008 3:32] Jared S
Description:
Hi,

Have logged this bug before and have new information which may help a developer fix a file handling exception in NET connector.

Basically I call an SP in NonQuery mode which update 1 table of 500K rows based upon index and then 1 more simple update.  10 minutes later when a Reader command is directly followed the NET/connector throw 0-Writing to the stream failed.

One thing to note is that I do use 2 connections and keep them both open in case I need to lookup suburb from another state.

How to repeat:
CODE1 : Open Connection1
CODE2 : Open Connection2 in same app
CODE3 : NonQuery(SP) Command on Connection1
CODE4 : 10 minutes of nothing
CODE5 : Reader Command on connection1

ERROR : 0 - Writing to stream failed

I think there is a MemoryStream conflict when using primary and secondry Connections to bypass the "data reader is already open error."

Appreciate comment from NET developer although I am unable to provide test case.
[27 May 2008 8:17] Jared S
Hardware\.NET20 error
[15 Jul 2008 2:56] Jared S
C# test case >> http://bugs.mysql.com/bug.php?id=38119