13 days ago
Hi Support Team,
I'm experiencing an issue with the internal connection between my web service and a MySQL database.
Right after deployment, everything works correctly and the connection is successfully established. However, after a certain period of time, the service is no longer able to connect to the database — the connection fails without any recent configuration changes. The issue seems to occur consistently after the service has been running for a while.
I'm using python connector for MySQL.
The error message: mysql.connector.errors.OperationalError: MySQL Connection not available.
I'm using an internal connection between the services, not an external or public endpoint.
Could you please help me identify the root cause or suggest how to debug and resolve this issue? Are there any common timeout settings, connection pool limits, or idle connection policies that might be affecting this?
If the issue persists and cannot be resolved in a reliable way, I may consider migrating the service to MongoDB instead.
Let me know if you need any additional information, such as logs or configuration details.
Best regards.
1 Replies
13 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open itsrems • 13 days ago
10 days ago
We resolved this issue by opening and closing the connection each time a query needs to be executed. Before, we opened the connection only once a new version of the app was deployed.
As I understood correctly from other threads, the connection to Mysql could be interrupted in case of inactivity or after a period of time.
Status changed to Open adam • 10 days ago
Status changed to Solved adam • 10 days ago
Status changed to Solved chandrika • 9 days ago