MySQL Bugs: #98111: MySQL stop connections

Bug #98111	MySQL stop connections
Submitted:	2 Jan 2020 18:15	Modified:	15 Jan 2020 18:01
Reporter:	Alice Tse	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	6.2	OS:	Windows (Windows Server 2012 R2)
Assigned to:		CPU Architecture:	Any

Description:
Under MySQL Server Logs, the error message is "Can't create thread to handle request (errno = 22).
Never seen this message before.

How to repeat:
I can't repeat it.

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php 

If you can provide more information, feel free to add it to this bug.

Thank you for your interest in MySQL.

The MySQL server is working normally in 24 hours/7 days. On 12/31/2019 at 5:17pm, my website was down with error message - "Error establishing a database connection". I checked that the MySQL server stopped connections.

Today, I checked the server logs of MySQL Server. I got the error message - Can't create thread to handle request (errno = 22).

The same error has happened again on Jan 14th 2020.
Please help.

Timestamp, Thread, Type, Details
2019-12-31 17:17:04, 1536, ERROR, Can't create thread to handle request (errno= 22)
2020-01-02 08:21:06, 1520, Note, Plugin 'FEDERATED' is disabled.
, , , 2020-01-02 08:21:06 6b0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2020-01-02 08:21:06, 1520, Note, InnoDB: Using atomics to ref count buffer pool pages
2020-01-02 08:21:06, 1520, Note, InnoDB: The InnoDB memory heap is disabled
2020-01-02 08:21:06, 1520, Note, InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-01-02 08:21:06, 1520, Note, InnoDB: Memory barrier is not used
2020-01-02 08:21:06, 1520, Note, InnoDB: Compressed tables use zlib 1.2.3
2020-01-02 08:21:06, 1520, Note, InnoDB: Not using CPU crc32 instructions
2020-01-02 08:21:06, 1520, Note, InnoDB: Initializing buffer pool, size = 949.0M
2020-01-02 08:21:06, 1520, Note, InnoDB: Completed initialization of buffer pool
2020-01-02 08:21:06, 1520, Note, InnoDB: Highest supported file format is Barracuda.
2020-01-02 08:21:06, 1520, Note, InnoDB: Log scan progressed past the checkpoint lsn 3743565086004
2020-01-02 08:21:06, 1520, Note, InnoDB: Database was not shutdown normally!
2020-01-02 08:21:06, 1520, Note, InnoDB: Starting crash recovery.
2020-01-02 08:21:06, 1520, Note, InnoDB: Reading tablespace information from the .ibd files...
2020-01-02 08:21:16, 1520, Note, InnoDB: Restoring possible half-written data pages
2020-01-02 08:21:16, 1520, Note, InnoDB: from the doublewrite buffer...
, , , InnoDB: Doing recovery: scanned up to log sequence number 3743565086014
2020-01-02 08:21:16, 1520, Note, InnoDB: 128 rollback segment(s) are active.
2020-01-02 08:21:16, 1520, Note, InnoDB: Waiting for purge to start
2020-01-02 08:21:17, 1520, Note, InnoDB: 5.6.22 started; log sequence number 3743565086014
2020-01-02 08:21:17, 1520, Note, Server hostname (bind-address): '*'; port: 3306
2020-01-02 08:21:17, 1520, Note, IPv6 is available.
2020-01-02 08:21:17, 1520, Note, - '::' resolves to '::';
2020-01-02 08:21:17, 1520, Note, Server socket created on IP: '::'.
2020-01-02 08:21:17, 1520, Note, Event Scheduler: Loaded 0 events
2020-01-02 08:21:17, 1520, Note, E:\Program Files (x86)\MySQL\MySQL Server 5.6\bin\mysqld.exe: ready for connections.
, , , Version: '5.6.22-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
2020-01-14 17:27:02, 1520, ERROR, Can't create thread to handle request (errno= 22)