com.javahollic.jira.emh.service.InvalidDirectiveDataException: Cannot handle message as destination project wasn't found

JIRA | Jordan Dea-Mattson | 7 years ago
  1. 0

    Have spent extensive time attempting to get projectDefault.KEY.domainMatches working with 0.9.3.7 and JIRA 4.0.1#471. If I do not define a *defaultProject*, I get the *_MessgingException: Unhandled Exception progressing issue (bug): Cannot handle message as destination project wan't found_* (see stack trace below). If I do set value of *defaultProject*, then no matter what address I use, *Project* is set to value of *defaultProject*. I have tried putting the setting of *defaultProject* both before and after my *projectDefault.KEY.domainMatches* lines in the configuration file. I have tested the regular expressions I am using and they match the *To:* address being used. Below I have provided both the configuration files I have tried to use. I know it is quite possible I am doing something stupid here and you will point it out, but I have gone through the documentation, our email conversations on the topic, the threads in JIRA and GetSatisfaction, and I am not seeing what I am missing if that is the case. It would seem that you need to have a defaultProject set, so that issues that do not match against a supplied *domainMatches* are properly processed. If that is not the case, I would assume that *domainMatches* are processed in order presented and I should supply a "match all" to handle issues not matches earlier. ---- *Configuration File without defaultProject set* {noformat} #### # Basic catch email JEMH configuration file #### #### # Overall JEMH settings ### # defaultIssueType is mandatory and we are setting it to 3, or bug. defaultIssueType=3 # defaultPriority is mandatory and we are setting it to P3 defaultPriority=P3 # defaultIssueLinkType is mandatory and we are setting it to relates defaultIssueLinkType=relates # Assign Default Projects via Regex of EMail Address projectDefault.QAITT.domainMatches=.*test\-jira\+qaitt@ooyala.com projectDefault.APP.domainMatches=.*test\-jira\+app@ooyala.com projectDefault.OTS.domainMatches=.*test\-jira\+ots@ooyala.com # List of packages to look for email processors, the default package contails full issue # creation support, CVS support and atlassian default handlers. Only classes that are # subclasses of AbstractFieldProcessor will be used emailFieldProcessorPackageList=com.javahollic.jira.emh.processor # What to do with the email which has F A I L E D processing (can't handle) deleteEmail=false #### # Processor settings #### # The number of empty lines at the head of the email body which can be safely ignored for # directive processing eatEmptyBodyLinesMax=2 # Capture the JEMH processor which processed this email. indicateWhichProcessorProcessedMail=true # Add users on the CC line as watchers. addWatchersFromCC=true #### # CommentHandler options #### # When people reply to Jira mails that end up in the EMH mailserver, the quoted content of those # mails can be stripped, or not (but this makes issues bigger and bigger and less readable) stripQuotes=true {noformat} ---- *Configuration File with defaultProject set* {noformat} #### # Basic catch email JEMH configuration file #### #### # Overall JEMH settings ### # defaultIssueType is mandatory and we are setting it to 3, or bug. defaultIssueType=3 # defaultPriority is mandatory and we are setting it to P3 defaultPriority=P3 # defaultIssueLinkType is mandatory and we are setting it to relates defaultIssueLinkType=relates # Assign Default Projects via Regex of EMail Address projectDefault.QAITT.domainMatches=.*test\-jira\+qaitt@ooyala.com projectDefault.APP.domainMatches=.*test\-jira\+app@ooyala.com projectDefault.OTS.domainMatches=.*test\-jira\+ots@ooyala.com # Assign Default Project, which will be overridden by our Project Default Regexes defaultProject=QAITT # List of packages to look for email processors, the default package contails full issue # creation support, CVS support and atlassian default handlers. Only classes that are # subclasses of AbstractFieldProcessor will be used emailFieldProcessorPackageList=com.javahollic.jira.emh.processor # What to do with the email which has F A I L E D processing (can't handle) deleteEmail=false #### # Processor settings #### # The number of empty lines at the head of the email body which can be safely ignored for # directive processing eatEmptyBodyLinesMax=2 # Capture the JEMH processor which processed this email. indicateWhichProcessorProcessedMail=true # Add users on the CC line as watchers. addWatchersFromCC=true #### # CommentHandler options #### # When people reply to Jira mails that end up in the EMH mailserver, the quoted content of those # mails can be stripped, or not (but this makes issues bigger and bigger and less readable) stripQuotes=true {noformat} ---- *Message Exception when defaultProject not set* {noformat} javax.mail.MessagingException: Unhandled Exception processing issue (bug): Cannot handle message as destination project wasn't found; nested exception is: com.javahollic.jira.emh.service.InvalidDirectiveDataException: Cannot handle message as destination project wasn't found at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:430) at com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssueHandler.java:130) at com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:67) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:189) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) Caused by: com.javahollic.jira.emh.service.InvalidDirectiveDataException: Cannot handle message as destination project wasn't found at com.javahollic.jira.emh.processor.BasicMailProcessor.getFieldMap(BasicMailProcessor.java:79) at com.javahollic.jira.emh.processor.BasicMailProcessor.extractFieldsAndBody(BasicMailProcessor.java:154) at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:252) ... 7 more {noformat} ----

    JIRA | 7 years ago | Jordan Dea-Mattson
    com.javahollic.jira.emh.service.InvalidDirectiveDataException: Cannot handle message as destination project wasn't found
  2. 0

    Have spent extensive time attempting to get projectDefault.KEY.domainMatches working with 0.9.3.7 and JIRA 4.0.1#471. If I do not define a *defaultProject*, I get the *_MessgingException: Unhandled Exception progressing issue (bug): Cannot handle message as destination project wan't found_* (see stack trace below). If I do set value of *defaultProject*, then no matter what address I use, *Project* is set to value of *defaultProject*. I have tried putting the setting of *defaultProject* both before and after my *projectDefault.KEY.domainMatches* lines in the configuration file. I have tested the regular expressions I am using and they match the *To:* address being used. Below I have provided both the configuration files I have tried to use. I know it is quite possible I am doing something stupid here and you will point it out, but I have gone through the documentation, our email conversations on the topic, the threads in JIRA and GetSatisfaction, and I am not seeing what I am missing if that is the case. It would seem that you need to have a defaultProject set, so that issues that do not match against a supplied *domainMatches* are properly processed. If that is not the case, I would assume that *domainMatches* are processed in order presented and I should supply a "match all" to handle issues not matches earlier. ---- *Configuration File without defaultProject set* {noformat} #### # Basic catch email JEMH configuration file #### #### # Overall JEMH settings ### # defaultIssueType is mandatory and we are setting it to 3, or bug. defaultIssueType=3 # defaultPriority is mandatory and we are setting it to P3 defaultPriority=P3 # defaultIssueLinkType is mandatory and we are setting it to relates defaultIssueLinkType=relates # Assign Default Projects via Regex of EMail Address projectDefault.QAITT.domainMatches=.*test\-jira\+qaitt@ooyala.com projectDefault.APP.domainMatches=.*test\-jira\+app@ooyala.com projectDefault.OTS.domainMatches=.*test\-jira\+ots@ooyala.com # List of packages to look for email processors, the default package contails full issue # creation support, CVS support and atlassian default handlers. Only classes that are # subclasses of AbstractFieldProcessor will be used emailFieldProcessorPackageList=com.javahollic.jira.emh.processor # What to do with the email which has F A I L E D processing (can't handle) deleteEmail=false #### # Processor settings #### # The number of empty lines at the head of the email body which can be safely ignored for # directive processing eatEmptyBodyLinesMax=2 # Capture the JEMH processor which processed this email. indicateWhichProcessorProcessedMail=true # Add users on the CC line as watchers. addWatchersFromCC=true #### # CommentHandler options #### # When people reply to Jira mails that end up in the EMH mailserver, the quoted content of those # mails can be stripped, or not (but this makes issues bigger and bigger and less readable) stripQuotes=true {noformat} ---- *Configuration File with defaultProject set* {noformat} #### # Basic catch email JEMH configuration file #### #### # Overall JEMH settings ### # defaultIssueType is mandatory and we are setting it to 3, or bug. defaultIssueType=3 # defaultPriority is mandatory and we are setting it to P3 defaultPriority=P3 # defaultIssueLinkType is mandatory and we are setting it to relates defaultIssueLinkType=relates # Assign Default Projects via Regex of EMail Address projectDefault.QAITT.domainMatches=.*test\-jira\+qaitt@ooyala.com projectDefault.APP.domainMatches=.*test\-jira\+app@ooyala.com projectDefault.OTS.domainMatches=.*test\-jira\+ots@ooyala.com # Assign Default Project, which will be overridden by our Project Default Regexes defaultProject=QAITT # List of packages to look for email processors, the default package contails full issue # creation support, CVS support and atlassian default handlers. Only classes that are # subclasses of AbstractFieldProcessor will be used emailFieldProcessorPackageList=com.javahollic.jira.emh.processor # What to do with the email which has F A I L E D processing (can't handle) deleteEmail=false #### # Processor settings #### # The number of empty lines at the head of the email body which can be safely ignored for # directive processing eatEmptyBodyLinesMax=2 # Capture the JEMH processor which processed this email. indicateWhichProcessorProcessedMail=true # Add users on the CC line as watchers. addWatchersFromCC=true #### # CommentHandler options #### # When people reply to Jira mails that end up in the EMH mailserver, the quoted content of those # mails can be stripped, or not (but this makes issues bigger and bigger and less readable) stripQuotes=true {noformat} ---- *Message Exception when defaultProject not set* {noformat} javax.mail.MessagingException: Unhandled Exception processing issue (bug): Cannot handle message as destination project wasn't found; nested exception is: com.javahollic.jira.emh.service.InvalidDirectiveDataException: Cannot handle message as destination project wasn't found at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:430) at com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssueHandler.java:130) at com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:67) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:189) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) Caused by: com.javahollic.jira.emh.service.InvalidDirectiveDataException: Cannot handle message as destination project wasn't found at com.javahollic.jira.emh.processor.BasicMailProcessor.getFieldMap(BasicMailProcessor.java:79) at com.javahollic.jira.emh.processor.BasicMailProcessor.extractFieldsAndBody(BasicMailProcessor.java:154) at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:252) ... 7 more {noformat} ----

    JIRA | 7 years ago | Jordan Dea-Mattson
    com.javahollic.jira.emh.service.InvalidDirectiveDataException: Cannot handle message as destination project wasn't found
  3. 0

    Getting this exception when retrieving any email from our exchange server. This was working until late last week, but we don't see what has changed. I tried a later mail.jar file (recommended on another forum) and the latest "snap" release (0.9.4.3 I think) and those actually introduced worse problems (e.g. couldn't even send email any longer). Note the email I sent to exchange was of Text type. 2010-05-24 10:07:13,347 JiraQuartzScheduler_Worker-0 ERROR ServiceRunner Jira Defects Email [jira.emh.service.EMHIssueHandler] Rethrowing exception: Unhandled Exception occurred during processing, type=com.javahollic.jira.emh.service.InvalidDirectiveDataException), location=com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProcessorHelper.java:119). Likely this is a BUG: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart javax.mail.MessagingException: Unhandled Exception occurred during processing, type=com.javahollic.jira.emh.service.InvalidDirectiveDataException), location=com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProcessorHelper.java:119). Likely this is a BUG: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart; nested exception is: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:497) at com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssueHandler.java:125) at com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:67) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:189) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) Caused by: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart at com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProcessorHelper.java:119) at com.javahollic.jira.emh.processor.BasicMailProcessor.extractFieldsAndBody(BasicMailProcessor.java:48) at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:279) ... 7 more Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart at com.javahollic.jira.emh.engine.EMHMailUtils.getAttachments(EMHMailUtils.java:160) at com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixupAttachments(AbstractFieldProcessorHelper.java:413) at com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProcessorHelper.java:104) ... 9 more

    JIRA | 7 years ago | Sean Curley
    com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    When forwarding an email which quotes another email, I'm seeing a class cast exception, included below. The email has multiple nested quoted emails, but no attachments. {quote} 2010-05-26 09:15:53,449 JiraQuartzScheduler_Worker-0 ERROR ServiceRunner ((dest email omitted)) : JEMH Handler [jira.emh.service.EMHIssueHandler] ==== CUT ===== 2010-05-26 09:15:53,450 JiraQuartzScheduler_Worker-0 ERROR ServiceRunner ((dest email omitted)) : JEMH Handler [jira.emh.service.EMHIssueHandler] Rethrowing exception: Unhandled Exception occurred during processing, type=com.javahollic.jira.emh.service.InvalidDirectiveDataException), location=com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProcessorHelper.java :119). Likely this is a BUG: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart javax.mail.MessagingException: Unhandled Exception occurred during processing, type=com.javahollic.jira.emh.service.InvalidDirectiveDataException), location=com.javahollic.jira.emh.engine.AbstractField ProcessorHelper.fixup(AbstractFieldProcessorHelper.java:119). Likely this is a BUG: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart; nested exception is: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:497) at com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssueHandler.java:125) at com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:67) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:189) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) Caused by: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart at com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProcessorHelper.java:119) at com.javahollic.jira.emh.processor.AtPrefixedFieldProcessor.extractFieldsAndBody(AtPrefixedFieldProcessor.java:257) at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:279) ... 7 more Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart at com.javahollic.jira.emh.engine.EMHMailUtils.getAttachments(EMHMailUtils.java:160) at com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixupAttachments(AbstractFieldProcessorHelper.java:413) at com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProcessorHelper.java:104) ... 9 more 2010-05-26 09:15:53,450 JiraQuartzScheduler_Worker-0 ERROR ServiceRunner ((dest email omitted)) : JEMH Handler [jira.emh.service.CreateOrCommentHandler] Unandled MessagingException: Unhandled Exception occurred during processing, type=com.javahollic.jira.emh.service.InvalidDirectiveDataException), location=com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProces sorHelper.java:119). Likely this is a BUG: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart 2010-05-26 09:17:43,780 JiraQuartzScheduler_Worker-0 ERROR ServiceRunner ((dest email omitted)) : JEMH Handler [jira.emh.engine.AbstractFieldProcessorHelper] Fixup failed (bug) class java.lang.ClassCastException : java.lang.String cannot be cast to javax.mail.internet.MimeMultipart 2010-05-26 09:17:43,780 JiraQuartzScheduler_Worker-0 ERROR ServiceRunner ((dest email omitted)): JEMH Handler [jira.emh.service.EMHIssueHandler] Jira Version = 1.6.1 (Build:#391 - Feb 17, 2009) 2010-05-26 09:17:43,780 JiraQuartzScheduler_Worker-0 ERROR ServiceRunner ((dest email omitted)) : JEMH Handler [jira.emh.service.EMHIssueHandler] Unhandled Exception occurred during processing, type=com.javahollic.jira.emh.service.InvalidDirectiveDataException), location=com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProcessorHelper.java:119). Likely this is a BUG: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart 2010-05-26 09:17:43,781 JiraQuartzScheduler_Worker-0 ERROR ServiceRunner ((dest email omitted)) : JEMH Handler [jira.emh.service.EMHIssueHandler] To: ... (email itself omitted) {quote}

    JIRA | 7 years ago | Rob Parrott
    com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart
  6. 0

    One of our users updated an issue manually to 'In Progress', shortly there after, another user sent an update email to Jira for the same issue. Note the email that was sent was to update the issue status to 'In Progress', the same as it was done manually. The NPE was thrown in our logs and the issue was actually move to a different status 'Awaiting Feedback'. I would expect the issue to stay as 'In Progress'. Is the space between the = and 'in progress' causing the error? EMAIL: From: Ibukun Sent: Thursday, May 13, 2010 12:14 PM To: Jira Issues Subject: RE: CR4200 - Promote updated custom Route Manifest v1.2 for Oldcastle - Prod FW-1564 @Workflow= in progress ---- javax.mail.MessagingException: Unhandled Exception occurred during processing, type=com.javahollic.jira.emh.service.InvalidDirectiveDataException), location=com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProcessorHelper.java:119). Likely this is a BUG: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart; nested exception is: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:497) at com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssueHandler.java:125) at com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:67) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:189) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) Caused by: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart at com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProcessorHelper.java:119) at com.javahollic.jira.emh.processor.BasicMailProcessor.extractFieldsAndBody(BasicMailProcessor.java:48) at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:279) ... 7 more Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart at com.javahollic.jira.emh.engine.EMHMailUtils.getAttachments(EMHMailUtils.java:160) at com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixupAttachments(AbstractFieldProcessorHelper.java:413) at com.javahollic.jira.emh.engine.AbstractFieldProcessorHelper.fixup(AbstractFieldProcessorHelper.java:104) ... 9 more

    JIRA | 7 years ago | Ryan Wilcox
    com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.internet.MimeMultipart

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.javahollic.jira.emh.service.InvalidDirectiveDataException

      Cannot handle message as destination project wasn't found

      at com.javahollic.jira.emh.processor.BasicMailProcessor.getFieldMap()
    2. com.javahollic.jira
      CreateOrCommentHandler.handleMessage
      1. com.javahollic.jira.emh.processor.BasicMailProcessor.getFieldMap(BasicMailProcessor.java:79)
      2. com.javahollic.jira.emh.processor.BasicMailProcessor.extractFieldsAndBody(BasicMailProcessor.java:154)
      3. com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:252)
      4. com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssueHandler.java:130)
      5. com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:67)
      5 frames
    3. com.atlassian.jira
      ServiceRunner.execute
      1. com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:189)
      2. com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67)
      3. com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48)
      3 frames
    4. quartz
      SimpleThreadPool$WorkerThread.run
      1. org.quartz.core.JobRunShell.run(JobRunShell.java:191)
      2. org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
      2 frames