Bug #36855 intermittent exception in table adapter
| Submitted: | 21 May 2008 16:19 | Modified: | 17 Jul 2008 14:06 |
|---|---|---|---|
| Reporter: | Ray Rizzuto | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | Connector / NET | Severity: | S1 (Critical) |
| Version: | 5.1.4.0 | OS: | Windows (Server 2003 R2) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | exception, invalid read closed, table adapter | ||
[21 May 2008 16:19]
Ray Rizzuto
[21 May 2008 16:37]
Ray Rizzuto
Sorry - development system is XP Pro SP2, but the error occurred on a deployed system running Server 2003 R2
[21 May 2008 16:42]
Ray Rizzuto
It is possible the DB Server closed the connection during the read. In the case where I saw this, 9 instances of the application were started within 6 seconds of each other. 8 of them complete reading the db via the table adapter ~ 1 minute later. The one instance that throws the exception does so after ~45 seconds - i.e. well into the read of the table, but before the read was complete. Here's the query, which I forgot to include previously: SELECT ssa_options.opt_susqus_symbol, ssa_options.opt_opra_symbol, ssa_cboe_product_ids.cboe_product_id FROM ssa_options LEFT OUTER JOIN ssa_cboe_product_ids ON ssa_options.opt_instrument_id = ssa_cboe_product_ids.instrument_id
[5 Jun 2008 23:10]
Ray Rizzuto
I have seen other cases of different exceptions, all apparently (not yet confirmed) due to a connection issue to the MySQL server: MySql.Data.MySqlClient.MySqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. MySql.Data.MySqlClient.MySqlException: There is already an open DataReader associated with this Connection which must be closed first.
[17 Jun 2008 13:51]
Tonci Grgin
Hi Ray and thanks for your report. I would like to posses that kind of magic to guess what's happening just by looking into trace... Please attach self sufficient test case exhibiting this behavior so I can check. In the meantime, please update to 5.1.7 and see if error persists.
[17 Jun 2008 13:56]
Ray Rizzuto
Hi! I do not see a 5.1.7 version of the connector on the web page yet, but I will try it as soon as it is available. I will see if I can come up with a test case. However, that is not a simple task for an intermittent issue. Is there any way I can better instrument my application to capture more detail when this does occur again? It hasn't happened for several days now. Ray
[17 Jun 2008 13:57]
Ray Rizzuto
FYI: I have seen this behavior with 5.1.6.0.
[17 Jun 2008 14:06]
Tonci Grgin
> Is there any way I can better instrument my application to capture more detail when this does occur again? It hasn't happened for several days now. Ray, try adding "logging=true" to your connection string. Also, starting server with --log and providing general query log + error log from server around the time error occurs might help (together with logging output). True, 5.1.7 is not out yet, sorry. Waiting on your test case.
[17 Jul 2008 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.042 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.