Bug #51309 | pooling=false; gives Object Reference is not set to an instance of an object | ||
---|---|---|---|
Submitted: | 19 Feb 2010 8:46 | Modified: | 19 Mar 2010 13:02 |
Reporter: | D Srinivas | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | Connector / NET | Severity: | S1 (Critical) |
Version: | .Net Connector 5.2.6.0 | OS: | Windows |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[19 Feb 2010 8:46]
D Srinivas
[19 Feb 2010 9:09]
Tonci Grgin
Hi Srinivas and thanks for your report. As current development version is 6.3 I have to ask you to use at least c/NET 6.2.2 and retest. 5.2.6 is way too old.
[19 Feb 2010 9:11]
Tonci Grgin
Btw, I had to be a wizard to figure bug out of just stack trace... You always have to attach small but complete test case which produces the error preferably every time we run it.
[19 Feb 2010 11:03]
D Srinivas
Hi Tonci, Thanks for your quick response. Is 6.2.2 Connect/NET works with MySQL 5.0.27 Server? Is it released? If so are there any special settings required in our web.config? Please let us know so that we start working on 6.2.2 Connect/NET. Yes, same error is coming once we set "pooling=false". Let me clarify from you one more thing here that shall we have to create any separate connection externally through our code when we set "pooling=false" or otherwise the usual process by instantiating the connection we can use the connection. Have a great day. Thanks once again.
[19 Feb 2010 13:02]
Tonci Grgin
Srinivas: > Is 6.2.2 Connect/NET works with MySQL 5.0.27 Server? Yes > Is it released? Yes. > If so are there any special settings required in our web.config? Please let us know so that we start working on 6.2.2 Connect/NET. This is unknown to me as I do not have your application. You should consider downloading the connector and checking on tests in "Test" folder. > Yes, same error is coming once we set "pooling=false". Let me clarify from you one more thing here that shall we have to create any separate connection externally through our code when we set "pooling=false" or otherwise the usual process by instantiating the connection we can use the connection. I do not get this at all, sorry... You are free to use or not to use pooling. The only thing you might pay attention on is max_connections server variable. However, new versions of c/NET do include completely new code for managing pools and timeouts so that might help you. You can find more in changelog and manual.
[20 Mar 2010 0: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".