com.javahollic.jira.emh.api.extension.fieldproc.FieldProcessorException

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.

  • I have a domain mapping for two emails {{logo@domain.de}} and {{logos@domain.de}}. The domain mapping is this regex: {noformat} logos{0,1}@domain\.de {noformat} If an email comes in I get a FieldProcessorException: {noformat} FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: Unclosed counted closure near index 7 logos{0 ^: com.javahollic.jira.emh.api.extension.fieldproc.FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: Unclosed counted closure near index 7 logos{0 ^ at com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:57) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:756) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:323) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:247) at com.javahollic.jira.emh.service.reprocessing.AuditHistoryNecromancer.reanimate(AuditHistoryNecromancer.java:85) at com.javahollic.jira.emh.service.DefaultJEMHAuditHistoryReprocessingManager.reanimate(DefaultJEMHAuditHistoryReprocessingManager.java:231) at com.javahollic.jira.emh.rest.api.auditing.Auditing.doReanimate(Auditing.java:136) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234) {noformat} This happens after updating JIRA from 5.1.8/JEMH 1.2.x to the latest versions. In the above mentioned combination this worked without problems.
    via by Henning Tietgens,
  • I have a domain mapping for two emails {{logo@domain.de}} and {{logos@domain.de}}. The domain mapping is this regex: {noformat} logos{0,1}@domain\.de {noformat} If an email comes in I get a FieldProcessorException: {noformat} FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: Unclosed counted closure near index 7 logos{0 ^: com.javahollic.jira.emh.api.extension.fieldproc.FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: Unclosed counted closure near index 7 logos{0 ^ at com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:57) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:756) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:323) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:247) at com.javahollic.jira.emh.service.reprocessing.AuditHistoryNecromancer.reanimate(AuditHistoryNecromancer.java:85) at com.javahollic.jira.emh.service.DefaultJEMHAuditHistoryReprocessingManager.reanimate(DefaultJEMHAuditHistoryReprocessingManager.java:231) at com.javahollic.jira.emh.rest.api.auditing.Auditing.doReanimate(Auditing.java:136) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234) {noformat} This happens after updating JIRA from 5.1.8/JEMH 1.2.x to the latest versions. In the above mentioned combination this worked without problems.
    via by Henning Tietgens,
  • I have status "forwarded exception" when JEMH tries to process an email that is a multi-part message in MIME format and has tow parts with content-disposition=inline (see attachment). Below the exception: FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.NullPointerException: com.javahollic.jira.emh.api.extension.fieldproc.FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.NullPointerException at com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:54) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:710) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:321) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:247) at com.javahollic.jira.emh.ui.action.JEMHTestCases.doRun(JEMHTestCases.java:246) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56) at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:433) at webwork.action.ActionSupport.execute(ActionSupport.java:157) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:82)
    via by Simone Zaninello,
  • Hi there, I've been trying to implement JEMH (Helpdesk scenario) with the most basic of config and at the moment cannot process any incoming email from either a JIRA or non user. The forwarded mail is as follows - Outcome forward Exception FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.NullPointerException: com.javahollic.jira.emh.api.extension.fieldproc.FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.NullPointerException at com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:57) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:756) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:323) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:247) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerProxy.handleMessage(EnterpriseMessageHandlerProxy.java:45) at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:368) at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:271) 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) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.NullPointerException Return-path: thanks, Gareth
    via by gareth,
  • When a Configuration > Project has only the Fall-Back Project and all other fields (project auto assign, auto assign from sub) blank and NO Project Mapping, a ticket is created in the Fall-back Project After a New Project Mapping is created for any project, I receive this error: FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: Name is null: com.javahollic.jira.emh.api.extension.fieldproc.FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: Name is null at com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:56) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:745) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:325) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:294) at com.javahollic.jira.emh.ui.action.JEMHTestCases.doRun(JEMHTestCases.java:378) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56) at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:438) at webwork.action.ActionSupport.execute(ActionSupport.java:157) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:87) This problem was introduced in v.42, config was working as expected in v.41
    via by Ed Chung,
  • I had a user trying to create an issue per e-mail which caused an exception. As it seems a "Content-Disposition: inline" e-mail header causes this. I tried to come up with a minimal example; see jemh-audithistory-203.txt in attached .eml. Exception: {noformat}FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to java.io.InputStream: com.javahollic.jira.emh.api.extension.fieldproc.FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to java.io.InputStream at com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:56) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:759) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:336) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:279) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerProxy.handleMessage(EnterpriseMessageHandlerProxy.java:45) at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:400) at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:293) at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:388) 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) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ClassCastException: java.lang.String cannot be cast to java.io.InputStream{noformat}
    via by Mike Dornberger,
  • I got this error today. Not sure why, or what this is referring to. The email in question contained a small message with a 10MB PDF Attachment. As far as i coulde see it was just the same as any "other" email. JEMH stopped collecting emails until i "removed" this mail from the innboks, it then started to process the other emails. Any ide why i get this error? Is it a bug? or a error in my enviroment? FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ArrayIndexOutOfBoundsException: message number (3) out of bounds (1): com.javahollic.jira.emh.api.extension.fieldproc.FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ArrayIndexOutOfBoundsException: message number (3) out of bounds (1) at com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:55) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:743) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:323) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:291) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerProxy.handleMessage(EnterpriseMessageHandlerProxy.java:45) at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:400) at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:293) at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:388) 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) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.ArrayIndexOutOfBoundsException: message number (3) out of bounds (1)
    via by Lasse Rolstad,
  • When a Configuration > Project has only the Fall-Back Project and all other fields (project auto assign, auto assign from sub) blank and NO Project Mapping, a ticket is created in the Fall-back Project After a New Project Mapping is created for any project, I receive this error: FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: Name is null: com.javahollic.jira.emh.api.extension.fieldproc.FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: Name is null at com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:56) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:745) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:325) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:294) at com.javahollic.jira.emh.ui.action.JEMHTestCases.doRun(JEMHTestCases.java:378) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56) at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:438) at webwork.action.ActionSupport.execute(ActionSupport.java:157) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:87) This problem was introduced in v.42, config was working as expected in v.41
    via by Ed Chung,
  • Hello, We’ve been having a problem recently where emails are failing to be processed and a null pointer exception is thrown. I haven’t been able to find any similarities between the emails rejected, and if I reprocess them, they go through without any issues. Seems to be happening an average of once a week. The error we get is: FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.NullPointerException: com.javahollic.jira.emh.api.extension.fieldproc.FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: java.lang.NullPointerException at com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:56) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:805) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:343) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:307) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerProxy.handleMessage(EnterpriseMessageHandlerProxy.java:46) at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:438) at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:304) at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:426) at com.atlassian.jira.service.services.file.AbstractMessageHandlingService.run(AbstractMessageHandlingService.java:263) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:66) at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:75) at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:53) at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:36) at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:135) - Joe
    via by Joseph Tillinghast,
    • com.javahollic.jira.emh.api.extension.fieldproc.FieldProcessorException: com.javahollic.jira.emh.service.InvalidDirectiveDataException: com.javahollic.jira.emh.service.EMHProcessingFailureException: ProjectMapper failed to fixup applyProjectMappingsForCreate: Unclosed counted closure near index 7 logos{0 ^ at com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:57) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:756) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:323) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:247) at com.javahollic.jira.emh.service.reprocessing.AuditHistoryNecromancer.reanimate(AuditHistoryNecromancer.java:85) at com.javahollic.jira.emh.service.DefaultJEMHAuditHistoryReprocessingManager.reanimate(DefaultJEMHAuditHistoryReprocessingManager.java:231) at com.javahollic.jira.emh.rest.api.auditing.Auditing.doReanimate(Auditing.java:136) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234)
    No Bugmate found.