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 ^

JIRA | Henning Tietgens | 3 years ago
  1. 0

    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.

    JIRA | 3 years ago | Henning Tietgens
    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 ^
  2. 0

    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.

    JIRA | 3 years ago | Henning Tietgens
    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 ^
  3. 0

    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

    JIRA | 3 years ago | Ed Chung
    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
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    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

    JIRA | 3 years ago | Ed Chung
    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
  6. 0

    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}

    JIRA | 2 years ago | Mike Dornberger
    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

    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.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()
    2. com.javahollic.jira
      Auditing.doReanimate
      1. com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:57)
      2. com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:756)
      3. com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:323)
      4. com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:247)
      5. com.javahollic.jira.emh.service.reprocessing.AuditHistoryNecromancer.reanimate(AuditHistoryNecromancer.java:85)
      6. com.javahollic.jira.emh.service.DefaultJEMHAuditHistoryReprocessingManager.reanimate(DefaultJEMHAuditHistoryReprocessingManager.java:231)
      7. com.javahollic.jira.emh.rest.api.auditing.Auditing.doReanimate(Auditing.java:136)
      7 frames
    3. Java RT
      Method.invoke
      1. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      2. sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      3. sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      4. java.lang.reflect.Method.invoke(Method.java:597)
      4 frames
    4. com.atlassian.plugins
      DispatchProviderHelper$ResponseOutInvoker$1.invoke
      1. com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234)
      1 frame