Details
-
Suggestion
-
Resolution: Obsolete
-
None
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
If there is a large amount of notifications and JIRA is unable to process an email, mail queue gets stuck and does not send any. It's possible to use the 'bypass' feature to move through the queue, but this is manual and might need to be done multiple times.
You can see this in the logs:
@400000005452b56217b5540c 2014-10-30 15:02:00,396 atlassian-scheduler-quartz1.clustered_Worker-2 ERROR ServiceRunner PEVS MBI [atlassian.mail.incoming.mailfetcherservice] PEVS MBI[10041]: Exception: com.sun.mail.smtp.SMTPSendFailedException: 552 5.3.4 Error: message file too big @400000005452b56217b55bdc @400000005452b56217b55fc4 com.atlassian.mail.MailException: com.sun.mail.smtp.SMTPSendFailedException: 552 5.3.4 Error: message file too big @400000005452b56217b55fc4 @400000005452b56217b55fc4 at com.atlassian.mail.server.impl.SMTPMailServerImpl.sendWithMessageId(SMTPMailServerImpl.java:201) @400000005452b56217b914fc at com.atlassian.mail.server.impl.SMTPMailServerImpl.send(SMTPMailServerImpl.java:149) @400000005452b56217b918e4 at com.atlassian.jira.service.services.mail.MailFetcherService$ErrorEmailForwarderImpl.sendMail(MailFetcherService.java:599) @400000005452b56217b91ccc at com.atlassian.jira.service.services.mail.MailFetcherService$ErrorEmailForwarderImpl.forwardEmail(MailFetcherService.java:561) @400000005452b56217b92884 at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:420) @400000005452b56217b92884 at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:306) @400000005452b56217b93ff4 at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:401) @400000005452b56217b943dc at com.atlassian.jira.service.services.file.AbstractMessageHandlingService.run(AbstractMessageHandlingService.java:261) @400000005452b56217b94bac at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:66) @400000005452b56217b972bc at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:75) @400000005452b56217b972bc at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:53) @400000005452b56217b976a4 at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:36) @400000005452b56217b97a8c at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:135) @400000005452b56217b9825c at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:101) @400000005452b56217b98644 at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:80) @400000005452b56217b98644 at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32) @400000005452b56217b98a2c at org.quartz.core.JobRunShell.run(JobRunShell.java:223) @400000005452b56217b98e14 at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
If this occurs, the bypass should be automatic or should allow for notifying administrators so that they can deal with this and not suffer prolonged outages.
Attachments
Issue Links
- is related to
-
JRASERVER-41495 Mail queue gets stuck when encountering a single mail too large to process, unable to recover
- Closed