MySQL Bugs: #106368: Connection pool cleanup is effectively disabled, but so easy to fix TG!

Bug #106368	Connection pool cleanup is effectively disabled, but so easy to fix TG!
Submitted:	3 Feb 2022 12:37	Modified:	9 Jun 2022 21:24
Reporter:	Karl Alexander	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / NET	Severity:	S3 (Non-critical)
Version:	Latest	OS:	Any
Assigned to:		CPU Architecture:	Any

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

Changes 1 of 4

Attachment: dif4.PNG (image/png, text), 81.50 KiB.

Changes 2 of 4

Attachment: dif3.PNG (image/png, text), 60.56 KiB.

Changes 3 of 4

Attachment: dif2.PNG (image/png, text), 24.01 KiB.

Changes 4 of 4

Attachment: dif1.PNG (image/png, text), 93.79 KiB.

The fixed MySqlPool using LinkedList<T> original code from version 8.0.18!

Attachment: MySqlPool.cs (text/plain), 11.23 KiB.

Production DB, connections open before and after fix

Attachment: ConnectionsProduction.PNG (image/png, text), 34.88 KiB.