Bug #104524 MY SQL DB service stops when used with Windows service + triggers
Submitted: 3 Aug 2021 16:30 Modified: 3 Aug 2021 16:41
Reporter: Neha Haridas Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Windows Severity:S1 (Critical)
Version:8.0 OS:Windows (2016 R2)
Assigned to: CPU Architecture:Other (64 bit)
Tags: windows service triggers

[3 Aug 2021 16:30] Neha Haridas
Description:
Background:
I have developed a windows service (scheduler) which is accessing the MYSQL database using the ado dot net connection.
MYSQL tables have some triggers applied on them which inserts data to my transaction tables.

Problem : 
The windows service is scheduled to run after every 5 mins. The service starts and dose the desired job with the database. After 5 - 7 consecutive runs the MYSQL DB service stops and gets the message " Unable to connect to the hosts".
Post this I have to manually start the MYSQL DB service from Windows services.

Solution tried:
1) I have tried to change the buffer and other settings as mentioned in some of the posts recommended by Google when searched for the issue.
2) Checked/Enables logs- but could not find the nerve.
3) Disabled triggers and then started the windows service -- This worked the database service did not stopped/crashed.

While the 3rd point worked for me, I am unable to resolve the issue as I need the trigger logic to work for my application.
Request your attention here, as soon we need to go live with the application and simple google search is not actually solving the problem.

How to repeat:
1) Windows service having ado dot net connection string
2) MY SQL table with a insert trigger applied to update data to another table
[3 Aug 2021 16:41] MySQL Verification Team
Thank you for the bug report. There is no problems to start/stop the MySQL service using the standard OS ways, so the issue is on your own procedure code which isn't supported here.