i see a lot of connection errors in the mysql server log file:
2018-01-20T00:57:48.888433Z 15848 [Note] Aborted connection 15848 to db: 'xx' user: 'xx' host: 'xxx' (Got timeout reading communication packets)
The connections are closed after the idle timeout is reached (400 seconds).
As far as i understand the configuration, this should not happen, because the validation query should be executed before:
JIRA Version: 7.7 and 7.5.1.
I did some research and found there are other possibilities for this behavior:
At this point try the following:
Please also take a look at the following resources as well:
Let me know what you find. If this doesn't help let me know and we'll go from there.
>Do you see any pattern to the users being disconnected in this manner?
I do not see any pattern.
There is no load on the server. Most of the time jira is idle: no user is logged in.
I think the reason is
The client slept for longer than the defined wait_timeout or interactive_timeout seconds (which ends up causing the connection to sleep for wait_timeout seconds and then the connection gets forcibly closed by the server)
But i thought that "time-between-eviction-runs-millis" and "pool-test-while-idle" should wake up the client. It seems that this is not happening.
I changed the following settings:
Now, idle connections are closed and i do not see the error messages any more.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot