The bug described in still happens with our Jira instance on the newest version of Issue Reminders. All issue reminders that are triggered by the application are sent at a 5 minute interval.
I have the atlassian-jira.log but they do not contain the "Acquiring cluster lock for sending reminders" wording that appeared when I sent logs to you in REM-178.
I have performed very extensive testing for todays release but I could not reproduce this problem. I'm sure that the problem caused by the exception shown in the debug logs you had send to me is fixed. But there may be another problem which I can't reproduce. Can you share your logs again after upgrading to latest version and just after the issue is reproduced. Please don't forget to increase log level of Issue Reminders as explained here.
Hello. We recently updated to 8.5.4 and are still seeing this this problem. I have sent logs to you. Let me know if you received them.
Thanks for the log file. I'm inspecting log file to understand why the transaction is rolling back for a while. I think I have found the problem. My theory is a periodic reminder created by a deleted user is causing this. I will test my theory but I wanted to notify you that I'm working on it. Sorry it is taking some time because although I can see that we can't commit transaction, it is not obvious why this happens.
Thank you for the update.
We have released 1.14.2 version which should fix this issue. Thanks for providing debug logs to us.