Symptoms

1. Mail Queue never flushes. A manual flush is required.
2. Mail queue service is configure to flush every 2 minutes, but it flushes only after very long time, e.g. every 75 minutes.
   If Mail queue service is configured to flush every 0 second(s) and you recently upgraded to JIRA 6.3.x (now JIRA Software), please set it to 1 minute.
3. There are strange jumps back and forth in the system time recorded (refer to log below)

The following appears in the atlassian-jira.log (with mail debugging enabled) :

2011-10-19 18:47:46,756 QuartzWorker-0 DEBUG ServiceRunner [org.quartz.core.JobRunShell] Calling execute on job DEFAULT.RefreshActiveUserCount
2011-10-19 18:47:46,780 _jiraSystemTenant-Scheduler_QuartzSchedulerThread DEBUG [org.quartz.simpl.SimpleJobFactory] Producing instance of Job 'DEFAULT.RefreshActiveUserCount', class="com".atlassian.jira.user.job.RefreshActiveUserCountJob
2011-10-19 18:47:46,781 QuartzWorker-0 DEBUG ServiceRunner [org.quartz.core.JobRunShell] Calling execute on job DEFAULT.RefreshActiveUserCount
2011-10-19 20:02:25,163 _jiraSystemTenant-Scheduler_QuartzSchedulerThread DEBUG [org.quartz.simpl.SimpleJobFactory] Producing instance of Job 'DEFAULT.ServicesJob', class="com".atlassian.jira.service.ServiceRunner
2011-10-19 18:49:07,118 QuartzWorker-0 DEBUG ServiceRunner [org.quartz.core.JobRunShell] Calling execute on job DEFAULT.ServicesJob

Cause

• The system time on the server where the JIRA application is installed is synching with an internet time server. This typically causes the system time to change regularly.
• If the JIRA application is executing 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.

Resolution

1. Disable time synchronization with the time server.

2. If this is occurring within RHEL, please contact RHEL support regarding bug 637069.

3. If you're running the JIRA applicaton inside a VMWare VM, please see this KB article for further information on a resolution.

Please refer to JRA-25836 - Getting issue details... STATUS for more information.