JIRA notification mail queue is hung in 5.1.3

[Vishnukumar Vasudevan]

After JIRA upgrade to 5.1.3 from 4.4.1, we don't get any notifications from JIRA.

When I went through mail queue, there was more than 1000 mails. I had to flush the queue to get mails delivered.

Is this a bug in 5.1.3 ? or should I make any changes in config ? Now, I am flushing mail queue once in an hour.

[Vishnukumar Vasudevan · Accepted solution]

Hi Luc

My issue was I had copied crowd-client jar file from my old JIRA instance. But for JIRA 5.1.x, it required new crowd-client jar file. Since I replaced this new file with old one, crowd sync worked abnormally. Which made the mail queue hung as both of these processes use same quartz service.

I could fix this issue when I copied the new crowd-client jar file

[Luc St-Laurent]

Hi Vishnu,

It's a fresh install of JIRA 5.2.

Luc

[Rich Fromm]

I'm curious if you ever got a decent answer to this. Related issues seem to be:

https://answers.atlassian.com/questions/72219/jira-5-0-email-delays

https://answers.atlassian.com/questions/125255/jira-email-delays

https://answers.atlassian.com/questions/201474/is-there-a-way-to-modify-the-threadcount-of-the-quartz-scheduler-in-jira

I'm seeing similar behavior, and so far my hacky solution has been to automate the pressing of the mail queue flush button once a minute. But next I'm looking at the quartz scheduler, as the third URL suggests.

[Luc St-Laurent]

Hi Vishnu,

It's a fresh install of JIRA 5.2.

Luc

[Luc St-Laurent]

Hi,

We have the same problem on JIRA 5.2.

The notification mail are stock in queue. The only way to send notification is to manualy flush mail queu or restart JIRA service.

• The Mail Queue service is set to 1 min.
• My JIRA is running within a VM on Windows but i dont have the "time jump" issue in the log.
• I don't have mail related error in log.
• JIRA have enought ressources

Do you have any solutions ?

Thank you :)

[Vishnukumar Vasudevan]

Better create a support ticket. They can rectify this by enabling debug logs for mail queue.

[Janet Albion]

You can start by checking the following:

• if there is Mail Queue service exist in the Administrations > Services
• check the delay for the Mail Queue service
• if JIRA is running within a Virtual Machine using RHEL, there is a known bug in the Redhat kernel which can generate a "time jump". Accessing the time kernel API can cause this problem. https://confluence.atlassian.com/display/JIRAKB/Mail+Queue+Never+Flushed+Automatically
• check if there any error thrown in the JIRA logs
• check if JIRA has sufficient resource (eg: memory) in the server

Check if the upgrade process is not affected by https://confluence.atlassian.com/display/JIRAKB/JIRA+Upgrade+Fails+with+Invalid+Column+Name+Error