edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.lang.NumberFormatException: null

Atlassian JIRA | Michael Tokar | 7 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    When trying to import a project with no {{assigneetype}} set, such as this: bq. {{<Project id="13274" name="Cusco" lead="u205339" key="GRCCUS" counter="172" />}} You get a NumberFormatException when you proceed to the actual import (i.e. past overview and mapping steps): {noformat} edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.lang.NumberFormatException: null at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:301) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:120) at com.atlassian.jira.task.TaskDescriptorImpl.getResult(TaskDescriptorImpl.java:113) at com.atlassian.jira.web.bean.TaskDescriptorBean.getResult(TaskDescriptorBean.java:78) at com.atlassian.jira.web.action.admin.importer.project.ProjectImportProgress.handleFinishedTask(ProjectImportProgress.java:32) at com.atlassian.jira.web.action.admin.importer.project.AbstractProjectImportProgress.doExecute(AbstractProjectImportProgress.java:61) ... Caused by: java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:372) at java.lang.Long.valueOf(Long.java:518) at org.ofbiz.core.entity.GenericEntity.setString(GenericEntity.java:286) at com.atlassian.jira.imports.project.DefaultProjectImportPersister.updateProjectDetails(DefaultProjectImportPersister.java:290) at com.atlassian.jira.imports.project.DefaultProjectImportManager.importProject(DefaultProjectImportManager.java:464) at com.atlassian.jira.bc.imports.project.DefaultProjectImportService.doImport(DefaultProjectImportService.java:423) at com.atlassian.jira.web.action.admin.importer.project.ProjectImportSummary$ProjectImportCallable.call(ProjectImportSummary.java:300) at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:360) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178) at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:252) {noformat} The presentation code of the assignee type in the Project Admin view seems to be able to handle {{null}} gracefully - the same should be done in Project Import (perhaps default to {{2}} = Project Lead?) h3. Update This bug only occurs when: * You are overwriting an existing project * The system you are importing from allowed unassigned issues

    Atlassian JIRA | 7 years ago | Michael Tokar
    edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.lang.NumberFormatException: null
  2. 0

    When trying to import a project with no {{assigneetype}} set, such as this: bq. {{<Project id="13274" name="Cusco" lead="u205339" key="GRCCUS" counter="172" />}} You get a NumberFormatException when you proceed to the actual import (i.e. past overview and mapping steps): {noformat} edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.lang.NumberFormatException: null at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:301) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:120) at com.atlassian.jira.task.TaskDescriptorImpl.getResult(TaskDescriptorImpl.java:113) at com.atlassian.jira.web.bean.TaskDescriptorBean.getResult(TaskDescriptorBean.java:78) at com.atlassian.jira.web.action.admin.importer.project.ProjectImportProgress.handleFinishedTask(ProjectImportProgress.java:32) at com.atlassian.jira.web.action.admin.importer.project.AbstractProjectImportProgress.doExecute(AbstractProjectImportProgress.java:61) ... Caused by: java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:372) at java.lang.Long.valueOf(Long.java:518) at org.ofbiz.core.entity.GenericEntity.setString(GenericEntity.java:286) at com.atlassian.jira.imports.project.DefaultProjectImportPersister.updateProjectDetails(DefaultProjectImportPersister.java:290) at com.atlassian.jira.imports.project.DefaultProjectImportManager.importProject(DefaultProjectImportManager.java:464) at com.atlassian.jira.bc.imports.project.DefaultProjectImportService.doImport(DefaultProjectImportService.java:423) at com.atlassian.jira.web.action.admin.importer.project.ProjectImportSummary$ProjectImportCallable.call(ProjectImportSummary.java:300) at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:360) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178) at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:252) {noformat} The presentation code of the assignee type in the Project Admin view seems to be able to handle {{null}} gracefully - the same should be done in Project Import (perhaps default to {{2}} = Project Lead?) h3. Update This bug only occurs when: * You are overwriting an existing project * The system you are importing from allowed unassigned issues

    Atlassian JIRA | 7 years ago | Michael Tokar
    edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.lang.NumberFormatException: null
  3. 0

    db:: 4.96::The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 3(@Parameter): Datatype0xF0 (User Defiend Type) has an invalid user type specified fd

    hivmr.com | 1 year ago
    edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.sql.SQLException: [GENSAPP12]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 3 (""): The supplied value is not a valid instance of data type datetime. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater than precision.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Operator Error

    Oracle Community | 9 years ago | Micropole
    edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.sql.SQLException: [GENSAPP12]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 3 (""): The supplied value is not a valid instance of data type datetime. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater than precision.

    Root Cause Analysis

    1. edu.emory.mathcs.backport.java.util.concurrent.ExecutionException

      java.lang.NumberFormatException: null

      at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult()
    2. Backport of JSR 166
      FutureTask.get
      1. edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:301)
      2. edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:120)
      2 frames
    3. com.atlassian.jira
      AbstractProjectImportProgress.doExecute
      1. com.atlassian.jira.task.TaskDescriptorImpl.getResult(TaskDescriptorImpl.java:113)
      2. com.atlassian.jira.web.bean.TaskDescriptorBean.getResult(TaskDescriptorBean.java:78)
      3. com.atlassian.jira.web.action.admin.importer.project.ProjectImportProgress.handleFinishedTask(ProjectImportProgress.java:32)
      4. com.atlassian.jira.web.action.admin.importer.project.AbstractProjectImportProgress.doExecute(AbstractProjectImportProgress.java:61)
      4 frames