Bug #23871 There is already an open DataReader (but no DataReader being used)
Submitted: 2 Nov 2006 4:07 Modified: 9 Nov 2006 8:18
Reporter: Smit Shah Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / NET Severity:S3 (Non-critical)
Version:5.0.24 OS:Windows (Windows XP)
Assigned to: CPU Architecture:Any

[2 Nov 2006 4:07] Smit Shah
Description:
There is already an open DataReader (but no DataReader being used)

How to repeat:
run the two script files

then 
execute these back to back

select meetingid, society, title
from is_meetings
where societyID=0
  and calendar='1'
  and date(CURDATE())>=startdate
  and date( date_add(CURDATE(),interval 7 day) )<=enddate;

select advboardid, btype, btopic
from is_advboard
where calendar='1'
  and date('11/1/2006')>=bdate
  and date('11/8/2006')<=bdate;
[2 Nov 2006 4:07] Smit Shah
Table 2

Attachment: is_advboard.sql (text/plain), 1.26 KiB.

[2 Nov 2006 4:07] Smit Shah
Table 1

Attachment: is_meetings.sql (text/plain), 12.10 KiB.

[3 Nov 2006 11:25] Tonci Grgin
Hi Smit and thanks for your problem report.
I will need some more info from you:
 - What is the connector/NET version?
 - What is the NET fw version?
 - Please post entire test case used to reproduce this behavior
[3 Nov 2006 13:38] Smit Shah
mysql connector 1.0.7.30072 dll
and Framework 1.1.4322

I simply created a page and tried to call these two queries from my .ascx.vb file and it failed
[3 Nov 2006 13:40] Smit Shah
one probable reason I can think of is... my main page has more than this control... there might be other controls using the same server to load data from different tables. so when its looking up for a connection from the pool its in use and hence it bombs out.

let me know what your take is on this
[9 Nov 2006 8:18] Tonci Grgin
Hi Smit. Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Explanation: Please upgrade to 1.0.8. See report BUG#19481 for details.