Issue Summary

After Jira's database is restarted, cache replication issues might occur.

Steps to Reproduce

1. Restart Jira's database with the application running

Expected Results

Jira connects to the database and continues to work normally, if configured correctly.

Actual Results

Jira typically reconnects to the database and resumes its operations normally.

In some cases, though, we start seeing the cache queue increasing to a point that the queue fills up and cache replication packages are consistently dropped.
This happen due to localq threads getting terminated after DB exceptions.
You can see the queue size in the logs. For example:

grep LOCALQ atlassian-jira.log*| grep -Eo '^.*"queueSize":\d*'

Workaround

Restart Jira. In Jira DC, a rolling restart can be performed to avoid downtime.