Proforma Server to Cloud failed JCMA migration with an 'Incomplete' status with 100% completion

XMLWordPrintable

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Low
    • 10.4.3
    • Affects Version/s: 10.3.2-DC
    • Component/s: API
    • 3
    • Minor

      Issue Summary

      ProForma Forms data is not migrating to Cloud as part of the JCMA migration

      Steps to Reproduce

      1. Jira 10.3.9 with ProForma 10.4.2-DC
      2. Perform JCMA migration

      Expected Results

      The Forms data is migrated successfully with no error messages.

      Actual Results

      The Forms data is not migrated and the below exception is thrown in the atlassian-jira.log file:

      [atlassian.migration.app.AbstractCloudMigrationRegistrar]  Failed to execute server listener for app-migration for transferId 85d4c771-aaa9-400d-8fb0-c5aa6fbf57a3, server app key com.thinktilt.proforma.add-on, cloud app key com.atlassian.proforma.proforma-migrator with exception:
      java.lang.reflect.InvocationTargetException: null
              at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
              at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:?]
              at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:?]
              at java.lang.reflect.Method.invoke(Unknown Source) ~[?:?]
              at com.atlassian.migration.app.DiscoverableListenerProxy.onStartAppMigration(DiscoverableListenerProxy.kt:57) ~[plugin.13816920650708593080.jira-migration-plugin-1.12.45.jar:?]
              at com.atlassian.migration.app.DiscoverableListenerProxy.onRerunAppMigration(DiscoverableListenerProxy.kt:94) ~[plugin.13816920650708593080.jira-migration-plugin-1.12.45.jar:?]
              at com.atlassian.migration.app.AbstractCloudMigrationRegistrar.executeRerun(AbstractCloudMigrationRegistrar.kt:248) ~[plugin.13816920650708593080.jira-migration-plugin-1.12.45.jar:?]
              at com.atlassian.migration.app.AbstractCloudMigrationRegistrar.executeTransfer(AbstractCloudMigrationRegistrar.kt:165) ~[plugin.13816920650708593080.jira-migration-plugin-1.12.45.jar:?]
              at com.atlassian.jira.migration.app.CloudMigrationRegistrar.runJob(CloudMigrationRegistrar.kt:365) ~[plugin.13816920650708593080.jira-migration-plugin-1.12.45.jar:?]
              at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134) ~[atlassian-scheduler-core-5.0.1.jar:?]
              at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106) ~[atlassian-scheduler-core-5.0.1.jar:?]
              at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90) ~[atlassian-scheduler-core-5.0.1.jar:?]
              at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:500) ~[atlassian-scheduler-caesium-3.1.4.jar:?]
              at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJobWithRetryOnFailure(CaesiumSchedulerService.java:463) ~[atlassian-scheduler-caesium-3.1.4.jar:?]
              at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:413) ~[atlassian-scheduler-caesium-3.1.4.jar:?]
              at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66) [atlassian-scheduler-caesium-3.1.4.jar:?]
              at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60) [atlassian-scheduler-caesium-3.1.4.jar:?]
              at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35) [atlassian-scheduler-caesium-3.1.4.jar:?]
              at java.lang.Thread.run(Unknown Source) [?:?]
      Caused by: java.lang.NullPointerException: Cannot invoke "java.lang.Integer.intValue()" because the return value of "java.lang.reflect.InvocationHandler.invoke(Object, java.lang.reflect.Method, Object[])" is null
              at jdk.proxy91.$Proxy6582.getServerPort(Unknown Source) ~[?:?]
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Lexi Weng
              Reporter:
              Chris Terry
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: