I saw some interesting behavior today that resulted in JIRA outgoing email not being sent for 18 hours, so there were 26K mail items to send. The outgoing mail log had an error about the mail queue being considered stuck, which apparently stops all mail from being sent. So I bypassed that first stuck mail item and flushed the queue. The mail queue then grew to 45K mail items before JIRA was able to get ahead of the flood!
There were no large bulk updates or scripts making large numbers of edits or huge subscriptions that I could see. Does anyone have ideas on what might have caused this? I'm scratching my head at the moment.
Also, the mail queue page doesn't show 45K lines of mail items, but I couldn't find where the limit is set on how many it does show. Perhaps something about webwork iterator has a limit?
This happened to one of our instance and the culprit was the ALMQC Synchronizer (Orasi). I cannot remember the exact reason but maybe a big. We also have found several accounts that are already inactive (so their email address is invalid) and JIRA was trying to send email to those. What we did was to set those accounts to "INACTIVE" so JIRA won't send email to those anymore.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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