com.javahollic.jira.emh.service.InvalidDirectiveDataException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Hi Andy, imagine the following situation: JEMH is configured to process mails of several Alias-email-adresses via domain mapping to several Projects (A,B,C). Another Admin has deleted project A from JIRA completely without telling us to disable the project and the domain mapping within the JEMH configuration. After this we experienced the following behaviour of the basic processor: * Mails to project B have been processed successfully * Mails to project C have been forwarded with exception (where "OZBVE" is the deleted project "A"): {quote} InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: locateDomainMatchForEmail: Project cannot be found (by name or KEY):OZBVE: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: locateDomainMatchForEmail: Project cannot be found (by name or KEY):OZBVE at com.javahollic.jira.emh.engine.AbstractFieldProcessorFixer.fixup(AbstractFieldProcessorFixer.java:155) at com.javahollic.jira.emh.processor.BasicMailProcessor.extractFieldsAndBody(BasicMailProcessor.java:48) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:553) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:191) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:218) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerProxy.handleMessage(EnterpriseMessageHandlerProxy.java:43) at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:356) at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:259) at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:344) 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) {quote} The problem occurred only for approx. 10% of the configured projects / domain mappings. Our junior has fixed the problem via GUI by the following workaround * adding the dummy project A to JIRA again, * removing the project/Domain mapping configuration in JEMH config and * deleting the dummy project A again. * resend the affected mails via Test Case tool I know, this case won't occur very often, but maybe the Exception / Bug report helps you to improve JEMH so that a missing projects don't have any influence for processing of emails mapped to other projects. Best regards, Kris
    via by Kristian Woitzick,
  • Hi Andy, imagine the following situation: JEMH is configured to process mails of several Alias-email-adresses via domain mapping to several Projects (A,B,C). Another Admin has deleted project A from JIRA completely without telling us to disable the project and the domain mapping within the JEMH configuration. After this we experienced the following behaviour of the basic processor: * Mails to project B have been processed successfully * Mails to project C have been forwarded with exception (where "OZBVE" is the deleted project "A"): {quote} InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: locateDomainMatchForEmail: Project cannot be found (by name or KEY):OZBVE: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: locateDomainMatchForEmail: Project cannot be found (by name or KEY):OZBVE at com.javahollic.jira.emh.engine.AbstractFieldProcessorFixer.fixup(AbstractFieldProcessorFixer.java:155) at com.javahollic.jira.emh.processor.BasicMailProcessor.extractFieldsAndBody(BasicMailProcessor.java:48) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:553) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:191) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:218) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerProxy.handleMessage(EnterpriseMessageHandlerProxy.java:43) at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:356) at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:259) at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:344) 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) {quote} The problem occurred only for approx. 10% of the configured projects / domain mappings. Our junior has fixed the problem via GUI by the following workaround * adding the dummy project A to JIRA again, * removing the project/Domain mapping configuration in JEMH config and * deleting the dummy project A again. * resend the affected mails via Test Case tool I know, this case won't occur very often, but maybe the Exception / Bug report helps you to improve JEMH so that a missing projects don't have any influence for processing of emails mapped to other projects. Best regards, Kris
    via by Kristian Woitzick,
  • Prior to installing your plugin we could send an email to the address associated with a specific jira project with no special fields defined and an issue would be created with defaults in that project. Now if I send an email to a specific jira project it doesn't make it through. Looking at the auditing I see the exception below. Note that I do have Fallback Project set in the Project->Defaults settings for my profile, and Project Auto assign and Auto Assign from Sub Addresses are both disabled. We need to be able to have issues created in the correct project without having users specify the project explicitly (they may just be forwarding an email to jira to create the issue). Profile export is attached. Example email is also attached. InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup projectDefaults: locateDomainMatchForEmail: Project cannot be found (by name or KEY):null: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup projectDefaults: locateDomainMatchForEmail: Project cannot be found (by name or KEY):null at com.javahollic.jira.emh.engine.AbstractFieldProcessorFixer.fixup(AbstractFieldProcessorFixer.java:133) at com.javahollic.jira.emh.processor.BasicMailProcessor.extractFieldsAndBody(BasicMailProcessor.java:48) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:451) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:170) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:202) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerProxy.handleMessage(EnterpriseMessageHandlerProxy.java:43) at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:356) at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:259) at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:344) 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)
    via by Kurt Matarese,
  • I defined a field and associated it with a project. Up until 1.2.67, I could use X-JEMH-customfield syntax and it would import properly. Now I get: InvalidDirectiveDataException: java.lang.NullPointerException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.NullPointerException at com.javahollic.jira.emh.engine.AbstractFieldProcessorFixer.fixup(AbstractFieldProcessorFixer.java:164) at com.javahollic.jira.emh.processor.XMailHeaderFieldProcessor.extractFieldsAndBody(XMailHeaderFieldProcessor.java:60) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:542) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:185) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:232) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerProxy.handleMessage(EnterpriseMessageHandlerProxy.java:44) at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:361) at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:264) 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) Interestingly a lookup still works (for example) X-JEMH-parentIssueKey: serverLogDate=2012-11-13
    via by Aaron Pelton,
  • I defined a field and associated it with a project. Up until 1.2.67, I could use X-JEMH-customfield syntax and it would import properly. Now I get: InvalidDirectiveDataException: java.lang.NullPointerException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.NullPointerException at com.javahollic.jira.emh.engine.AbstractFieldProcessorFixer.fixup(AbstractFieldProcessorFixer.java:164) at com.javahollic.jira.emh.processor.XMailHeaderFieldProcessor.extractFieldsAndBody(XMailHeaderFieldProcessor.java:60) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:542) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:185) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:232) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerProxy.handleMessage(EnterpriseMessageHandlerProxy.java:44) at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:361) at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:264) 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) Interestingly a lookup still works (for example) X-JEMH-parentIssueKey: serverLogDate=2012-11-13
    via by Aaron Pelton,
    • com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: locateDomainMatchForEmail: Project cannot be found (by name or KEY):OZBVE at com.javahollic.jira.emh.engine.AbstractFieldProcessorFixer.fixup(AbstractFieldProcessorFixer.java:155) at com.javahollic.jira.emh.processor.BasicMailProcessor.extractFieldsAndBody(BasicMailProcessor.java:48) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:553) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:191) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:218) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerProxy.handleMessage(EnterpriseMessageHandlerProxy.java:43) at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:356) at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:259) at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:344) 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)
    No Bugmate found.