After 2.3-OD-08 release, few email configurations disappeared from the list

XMLWordPrintable

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      This bug caused partially broken state for few email configurations while migrating over to new email infrastructure. The symptom is

      • Missing configuration
      • Re-adding configuration using same email address won't work (the error message should be the same as attachment)

      This bug doesn't affect functionalities of migrated, newly created email configuration.

      After the Cloud Service Desk release on February 8th, 2015, SD Email Server had its configuration missing. Customers tried to add it back (JIRA Service Desk Name >> Settings >> Email Settings) but the following error shows up:

      It reads:

      Error
Unable to create new mail channel due to connection duplication. Provided mail connection definition is currently used by another mail channel.

      When checking the SD Email Handler, we can see this:

      It reads:

      Mail handler used by JIRA Service Desk. Do not modify or delete. 10,306
Service Desk Mail Handler Local Files SD_MAIL_SERVER_ID: 10306

      On the logs we found:

      2015-02-09 15:58:31.607473500 java.lang.NullPointerException
2015-02-09 15:58:31.607474500 	at com.atlassian.servicedesk.squalor.email.ServiceDeskMailFetcherService.runImpl(ServiceDeskMailFetcherService.java:87)
2015-02-09 15:58:31.607483500 	at com.atlassian.jira.service.services.file.AbstractMessageHandlingService.run(AbstractMessageHandlingService.java:263)
2015-02-09 15:58:31.607484500 	at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:66)
2015-02-09 15:58:31.607484500 	at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:76)
2015-02-09 15:58:31.607485500 	at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:54)
2015-02-09 15:58:31.607486500 	at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:37)
2015-02-09 15:58:31.607486500 	at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:136)
2015-02-09 15:58:31.607487500 	at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:101)
2015-02-09 15:58:31.607490500 	at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:80)
2015-02-09 15:58:31.607491500 	at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32)
2015-02-09 15:58:31.607491500 	at org.quartz.core.JobRunShell.run(JobRunShell.java:223)

        1. error.png
          error.png
          20 kB
        2. error2.png
          error2.png
          47 kB

            Assignee:
            Duc Anh Dao (Inactive)
            Reporter:
            Jaime S
            Votes:
            5 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated:
              Resolved: