EF Core 1.3 Error timeout expired max pool size

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Post Reply
keng
Posts: 6
Joined: Wed 01 Feb 2017 02:33

EF Core 1.3 Error timeout expired max pool size

Post by keng » Mon 19 Mar 2018 03:04

Hi

I have error timeout max pool size. How to fix it.
I use Devart dotConnect for MySQL 8.10.1031 and ef core 1.3

image error => https://ibb.co/kc6V0H

Please help me.
Thank you for answer

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: EF Core 1.3 Error timeout expired max pool size

Post by Shalex » Mon 19 Mar 2018 15:55

dotConnect for MySQL uses connection pooling. If Pooling=true (the default value), the connection is not deleted after closing it, it is placed to the pool instead. When a new connection with the same connection string is opened, it is taken from the pool (if there are free connections) instead of the creating a new one. This provides significant performance improvements.
In case Pooling=false, a connection will be deleted from memory and free the session. However this may lead to performance loss.

With Pooling=true, make sure that you close connections after using them in your code. Notify us about the result.

keng
Posts: 6
Joined: Wed 01 Feb 2017 02:33

Re: EF Core 1.3 Error timeout expired max pool size

Post by keng » Wed 21 Mar 2018 07:24

Hi Shalex,

Thank you for information. It's work when close connection before a change connection runtime.

Post Reply