Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
The Plugin People
Teams
, (opens new window)
Knowledge Base
  • How-to articles
    How-to articles
     This trigger is hidden
Results will update as you type.
  • MYSQL Duplicate entry '0'. No Valid License
  • Non-JIRA recipient custom field values have been updated but JEMH is notifying the old values
  • Notification History tab does not show on issues
  • Problems with IMAP
  • Problems with POP
  • Slow Jira startup with PostgreSQL
  • Sorry, you can't create any issues right now, as you need to have access to a JIRA application to be able to create issues
  • You do not have permission to assign issues
  • How to change the event type of a notified event
  • Diagnose no inbound mail handled
  • JSD (Jira Service Desk) - Who is notified when?
  • HTML extraction method to Wiki mark up
  • Setting System Fields using Script Field Processor
  • Test case editor fails to load
  • MessageRemovedException in log files during email processing
  • Characters appearing as question marks
  • UI not visible after upgrading to version 3+
  • Default Project Mapping and unwanted inheritance causing inbound mail to be forwarded
  • JEMH is disabled on startup in Manage Apps
  • Configure JSD Customers for use with JEMH
  • Custom Field values are cached causing recipients to not receive notifications (JIRA 7.3.0 - 7.3.4 , JEMH 2.1.0 - 2.1.11)
  • Restrict commenting to one project
  • Foreign key constraint violation during Audit Event history purge
  • Request participants not sent JEMH notification
  • Handling out of disk space
  • Profile import timeout error
  • Zendesk integration
  • Outlook sending formatting
  • Attachment links added as comments, Jira Service Management/Desk
  • Incoming Auditing Actions Error Popup
  • Updating JEMH's issue event listener to listen for IssueEventBundle's (JEMH-6994)
  • Template Set Responsibility Devolution (JEMH-5403)
  • Support non-ascii characters in email addresses (JEMH-6431)
  • Custom Fields don't get added during creation phase causing creation notifications to not fire for User/Group field types. (JEMH-306)
  • Cant stop reporter being added as a watcher (JEMH-790)
  • Handle re-index failure during watcher setup (JEMH-7180)
  • Inline User Macros sometimes don't render (velocity 2.0 needed) (JEMH-5536)
  • "Stuck" emails in queues after post condition test (JEMH-5366)
  • Dealing with 'Undisclosed Recipients' (JEMH Server/DC)
  • Missing Methods in TemplateIssue Class since Jira 8.19.0
  • Why do FolderClosedException occur
  • Customer Permissions for Request Participants
  • User Anonymization Fails - SQL Server 2019
  • Maintaining JEMH Attachment Property Set values
  • Display Issue Notifications in Right To Left Languages
  • Jira Server/DC - when mail polling stops, fixing without a Jira restart
  • A3 BAD User is authenticated but not connected error message when using JIRA with Office365
  • JEMH not enabling on upgrade to Jira 8.13.x and 8.20.x LTS releases made after 23-MAY-2022
  • Using an inactive user with user creation enabled
  • Missing Created/Timestamp Columns Causing Problems
  • -1 Values for the "Comment count limit" and "Comment char length limit" in the Default Project-Mapping
    Calendars
You‘re viewing this with anonymous access, so some content might be blocked.
/
Why do FolderClosedException occur
Updated Aug 08

    Why do FolderClosedException occur

    • 1 Why does it happen
      • 1.1 Too many concurrent logins using the same account
      • 1.2 Mails are taking too long to download
        • 1.2.1 JEMH
        • 1.2.2 JEMHC
      • 1.3 When I see FolderClosed, is that a bug?
    • 2 JEMH Specific diagnostics
      • 2.1 What you see in JEMH Auditing
      • 2.2 Do you have clones of PROD environments running for test?
        • 2.2.1 JEMH Logs

    Why does it happen

    Your mailserver can drop connections for two main reasons:

    Too many concurrent logins using the same account

    Your mailserver may simply kill off the one that is oldest, which was unfortunately still in use. To check if this is a problem, count how many inbound mail servers you have defined using the same account. If its more than 15 you could be affected.

    Mails are taking too long to download

    The mailserver may determine the connection ‘dead’ if it takes too long to complete, caused by large emails taking too long.

    JEMH

    To verify if this problem affects you, and action you can take to increase the default batching size as described in Download performance of POP vs IMAPPreview.

    If you have just upgraded your Jira, check that you have migrated the customization to the environment (eg setenv.sh)

    JEMHC

    JEMHC automatically sets the properties to avoid batch size related problems.

    When I see FolderClosed, is that a bug?

    No, this is not a bug, it's just the consequence of your mail-server closing the connection to JEMH/C whilst the mail was still being read (by JEMH). It is not caused by JEMH/C and cannot be solved by JEMH/C. See Impact and Migration steps possible:

    When a FolderClosedException occurs, it stops all mail processing, specifically, as the mail was not read fully:

    • it was not processed at all, will not be consumed / marked read and will be retried

    • it will not be available in JEMH Auditing and cannot be exported as part of the support zip

    JEMH Specific diagnostics

    What you see in JEMH Auditing

    Current versions of JEMH prevent the ‘download’ button operating and show the following information dialog:

    The popup links to Download performance of POP vs IMAPPreview and an Atlassian article:
    IMAP mail fails with FolderClosedException in logs in Jira server | Jira and Jira Service Management | Atlassian Support .

    Do you have clones of PROD environments running for test?

    A reason that the mail can be not processed by this JEMH instance is that some other mail retrieval process may be ‘eating’ mail from the same mailbox (stealing mail). In such a case, the other instance was already processing the mail, marked it read/removed, such that the call from this JEMH instance was unable to find the mail.

    JEMH Logs

    Below is a stack trace error for the FolderClosedException that shows up in the 'atlassian-jira-incoming-mail.log', jemh.log and the JEMH processing Report.

    2013-07-12 09:52:50,478 ERROR [xxx] QuartzScheduler_Worker-3 ServiceRunner xxxx[xxxxx]: 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:257) at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:356) at com.atlassian.jira.service.services.file.AbstractMessageHandlingService.run(AbstractMessageHandlingService.java:257) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
    {"serverDuration": 9, "requestCorrelationId": "7f1dd0de2d80423b9994f436f61bd0fe"}