Bug #34961 | Unable to read data from the transport conn: An established conn was aborted by | ||
---|---|---|---|
Submitted: | 29 Feb 2008 12:24 | Modified: | 29 Feb 2008 19:11 |
Reporter: | Tonci Grgin | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / NET | Severity: | S1 (Critical) |
Version: | 5.1.4GA | OS: | Windows (XP, Vista) |
Assigned to: | CPU Architecture: | Any |
[29 Feb 2008 12:24]
Tonci Grgin
[29 Feb 2008 18:03]
Bogdan Degtyariov
This bug is very hard to diagnose. So far I tried the following: 1. Closing connections immediately after they are used 2. Disabling driver pooling 3. Increasing the number of TCP ports by tweaking registry keys 4. Simplifying the structure of the application 5. Connecting to remote MySQL server instead of localhost The test still throws exceptions
[29 Feb 2008 19:10]
Bogdan Degtyariov
It seems that the problem repeated with MS SQL Server. It didn't throw the exception like MySQL Connector/NET, but exception occurred when opening TcpServerChannel(). This is highly unlikely to be a bug in the Connector/NET.