Devart Forums

Corelab.MySql driver version 3.55.17

When Pooling is turned on, even after the connection is disposed, the following unhandled exception is raised when the process ends causing a process crash. Is Pooling not fully supported with SSL? Could you explain why this is happening and if there are any workarounds other than disabling pooling?

Thanks.

--------------------------------------------------------------

Exception: System.ObjectDisposedException

Message: Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'.

StackTrace: at System.Net.Sockets.Socket.SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName optionName, Int32 optionValue)
at CoreLab.Security.SSL.v.b(SocketOptionLevel A_0, SocketOptionName A_1, Int32 A_2)
at CoreLab.Security.SSL.n.c(Int32 A_0)
at CoreLab.MySql.j.a(Int32 A_0)
at CoreLab.MySql.b.a(am A_0, Byte[] A_1, Int32 A_2, Boolean A_3)
at CoreLab.MySql.b.m()
at CoreLab.MySql.r.v()

---------------------------------------------------------------

This happens when you open a connection using ssl and Pooling=True and close it and dispose it without doing any query.

This exception is handled by our provider in the latest 3.x version (3.55.26). Please upgrade to 3.55.26 if you want to stay with 3.x.
We recommend using the latest version of dotConnect for MySQL (5.80.152 or 6.0.10 Beta).

Thanks for response. We are planning to upgrade to a newer version of your drivers in next release.