We recently upgraded to JIRA 5.0 from 4.1. After doing this we noticed that when someone creates/updates an issue, JIRA sends out the notification emails one at a time in intervals of about 15 seconds. We did nothing different when setting up 5.0 with mail handlers and the SMTP mail server settings. We did migrate at this time to a new exchange server. We have tried many things to JIRA to send out the emails in bulk but nothing is working. Any help would be appreciated.
No, we can confirm that this issue has nothing to do with Exchange. We can see the emails being generated from JIRA in real time coming into exchange in approx. 15 second intervals which exchange is handling and sending out immediatly as it should. We need JIRA to be sending the notifications in bulk to exchange which is not happening.
I see in this in the logs:
2012-07-19 14:10:09,924 ERROR [scheduler_Worker-3] [atlassian.crowd.directory.DbCachingDirectoryPoller] pollChanges Error occurred while refreshing the cache for directory [ 13959170 ].
com.atlassian.crowd.exception.OperationFailedException: Unable to synchronise directory: duplicate groups with name 'Exchange Domain Servers'
2012-07-19 14:12:04,437 WARN [StreamsCompletionService::thread-8443] [atlassian.streams.internal.ActivityProviderConnectionMonitorImpl$ActivityMonitorJob] call Could not reach provider Release Management CI Instance; it will be omitted from the stream. The connection will be retried in 5 minutes
Could this be causing a problem?
Caused by: javax.mail.AuthenticationFailedException
... 17 more
2012-07-19 12:37:04,437 WARN [StreamsCompletionService::thread-8386] [atlassian.streams.internal.ActivityProviderConnectionMonitorImpl$ActivityMonitorJob] call Could not reach provider Release Management CI Instance; it will be omitted from the stream. The connection will be retried in 5 minutes
I did some more digging and found this error:
2012-07-19 12:34:15,575 ERROR [scheduler_Worker-2] [atlassian.core.task.AbstractErrorQueuedTaskQueue] handleException com.atlassian.mail.MailException: javax.mail.AuthenticationFailedException
User -Dmail.debug to see what's happening. IMHO, because you have AuthenticationFailedException, it is something linked to your new exchange server configuration.
Could it be that the default throttling is now in place on Exchange, and wasn't before? I'd recommend using a staging JIRA instance to see whether JIRA is trying to send the emails at long intervals, or whether it is trying and getting lots of 'not ready' responses from Exchange.
This message is also repeating when i look at the catalina logs:
2012-05-22 16:09:42,806 IssueIndexer:thread-5 WARN administrator 951x198x1 xdausq 192.168.201.136 /secure/admin/XmlRestore.jspa [atlassian.jira.web.FieldVisibilityManagerImpl] Issue with id '141210' and key 'CENSUS-6142' has a null project, returning true for isFieldHidden check.
When we upgraded we did switch in new hardware. People have metioned message throttling but we have never heard about that so what are some recommendations for setting those policies. Our exchange only accepts the email we give it and JIRA is the one making the email and using exchange as the sender.
JIRA doesn't track outbound notifications so no. It would result in millions of notification entries, JIRA dropping 'inbound' receipt records recently, it was a common cause of complaint taking up GB in big instances.
JEMH has some support for recording outbound notifications, but is meant for targetted projects, to avoid the problems of space above.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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