Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,320
Community Members
 
Community Events
176
Community Groups

Incoming Mail Handler: ERROR SerivceRunner atlassian.mail.incoming.mailfetcherservice

Receiving the following message in the logs. In fact we receive so many that the logs will fill up, filling up the filesystem then halting the system if we don't stay on top of things.

2013-02-05 08:09:56,445 QuartzWorker-0 ERROR ServiceRunner    EmailAccount [atlassian.mail.incoming.mailfetcherservice] EmailAccount[10400]: Exception: null
javax.mail.FolderClosedException
    at com.sun.mail.imap.IMAPMessage.getProtocol(IMAPMessage.java:145)
    at com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:743)
    at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:250)
    at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:349)
    at com.atlassian.jira.service.services.file.AbstractMessageHandlingService.run(AbstractMessageHandlingService.java:250)
    at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
    at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
    at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

Removed and recreated the Incoming Mail Handler, reset the password for the email account. Tested within Jira with success. Still receiving the errors during the email parsing in the logs. Ran updates to plugins without errors.

Any assitance is greatly appreciated.

2 answers

1 accepted

1 vote
Answer accepted

Removed a field that wasn't really needed as required. Once this field was removed from the create screen, the mail fetcher started operating as expected.

ConradR Rising Star Feb 04, 2013

Just curious: Which field?

On the "add" screen for this project, i made a field manditory (attachment). Although the error didn't state which field was the culprit, I was able to identify through process of elimination.

0 votes
richie_gee Atlassian Team Feb 04, 2013

Hi there,

I have seen issues on this resolved by increasing the timeout period, can you try check if this resolved your problem.

Alternatively, you can check if your bulk forward email is set to deliver to the same folder that your mail handler process, this might be the one causing this. Set the bulk forward to another account or different folder see if this fixes your problem.

Hope this helps, cheers!

Thanks for you reply Richie.

After further digging I found a hint to go on, "Exception: null". This led me to investigate the "required" fields on the create screen for this project. Once I removed the field that wasn't really needed as required, messages started flowing properly.

richie_gee Atlassian Team Feb 05, 2013

Hi Bob,

Glad to hear that you managed to resolve it locally and sharing out with the community :)

Thank you and have a great day ahead :)

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events