Timeout after idle time (MariaDB Server 10.3.39 (x86_64 Linux))
SmileYzn opened this issue Β· comments
Describe the bug
The query stop working after a idle time in MariaDB Server 10.3.39 (x86_64 Linux)
I need to disconnect and reconnect to db after
Ps. i think is that related to issue #577
To Reproduce
Steps to reproduce the behavior:
- new Query
- do a query
- Wait some minutes
- Do a new query and stopped working (ECONNECTION RESET)
Expected behavior
Do not need to disconnect / reconnect to db
SHOW SESSION VARIABLES LIKE '%_timeout%';
connect_timeout | 10
deadlock_timeout_long | 50000000
deadlock_timeout_short | 10000
delayed_insert_timeout | 300
idle_readonly_transaction_timeout | 0
idle_transaction_timeout | 0
idle_write_transaction_timeout | 0
innodb_flush_log_at_timeout | 1
innodb_lock_wait_timeout | 50
innodb_rollback_on_timeout | OFF
interactive_timeout | 28800
lock_wait_timeout | 86400
net_read_timeout | 30
net_write_timeout | 60
rpl_semi_sync_master_timeout | 10000
rpl_semi_sync_slave_kill_conn_timeout | 5
slave_net_timeout | 60
thread_pool_idle_timeout | 60
wait_timeout | 28800
Application (please complete the following information):
- App client MariaDB Server 10.3.39 (x86_64 Linux)
- App version MariaDB Server 10.3.39 (x86_64 Linux)
- Installation source: Windows
Environment (please complete the following information):
- OS name: Windows 11
- OS version 21H2
- DB name MariaDB
- DB version 10.3.39
Additional context
I using timeout setting for 5 seconds
Hi Cleverson,
Do you have a chance to install the future beta version?
I have implemented a mechanism to handle ECONNRESET with a reconnect attempt and would appreciate your feedback. Unfortunately, I cannot exactly replicate your condition.
Yes I can test it
I just released the new beta.
Thanks, i will test it π
Seems to be fixed, i do a query, wait for 5 minutes and do not having more timeout or connection resets π
It's possible that same error happens on click above a table to edit table options or just view it's contents?
It happen that bug on click on tables too
Ps. I did not have an idea if beta update includes table operations on left side
It's possible that same error happens on click above a table to edit table options or just view it's contents?
Could be.
What about queries has stopped happening instead?
Are you connected via SSH tunnel?
I have replicated the same DB settings but cannot replicate this problem.
However, I assume it is due to the connection pool and that is why I point to implementing an option to disable the pool mode.
I will let you know as soon as it is in beta.
Thanks again π
Ps.
I'm using the antares-sql in a daily work.
That connection reset is not a big problem.
Since first versions, antares works good on MySQL and MariaDB used on your servers!
I released in beta the feature to enable single connection mode (it is an option of the connection).
Let me know if enabling it makes the problem go away.
Genial, it's seems to be finxed:
My host seems to have problems with multiple connections at DB Server.
π