Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-703

CCMA plan can get stuck if an analytic event is bigger than 15.7 MB

    XMLWordPrintable

Details

    • 1
    • Minor

    Description

      Issue Summary

      When you do a space migration using the confluence cloud migration assistant if an analytic event is created and has more than 15.7 MB, it will render an error in the logs and make the plan stuck.

      Steps to Reproduce

      1. Create a plan with CCMA
      2. Start the plan with CCMA

      Expected Results

      Migration proceeds.

      Actual Results

      The plan will be stuck at 0% and in the logs, you will find the following exception:

      The below exception is thrown in the atlassian-confluence.log file:

      2021-07-11 19:51:45,837 ERROR [Caesium-1-3] [agent.service.analytics.AnalyticsEventConsumer] error An unhandled exception occurred when processing a AnalyticsEventConsumer job request. Reason: Bad request. Status code: 413, message: {
          "code": 105,
          "message": "Request content exceeded limit of 15728640 bytes"
      }
      com.atlassian.migration.agent.okhttp.HttpServiceException: Bad request. Status code: 413, message: {
          "code": 105,
          "message": "Request content exceeded limit of 15728640 bytes"
      }
      com.atlassian.migration.agent.okhttp.DefaultHttpServiceErrorHandler.accept(DefaultHttpServiceErrorHandler.java:21)
      com.atlassian.migration.agent.okhttp.DefaultHttpServiceErrorHandler.accept(DefaultHttpServiceErrorHandler.java:12)
      com.atlassian.migration.agent.okhttp.ServiceErrorCodeHandler.accept(ServiceErrorCodeHandler.java:26)
      com.atlassian.migration.agent.okhttp.ServiceErrorCodeHandler.accept(ServiceErrorCodeHandler.java:13)
      	at com.atlassian.migration.agent.okhttp.HttpService.callImpl(HttpService.java:122)
      	at com.atlassian.migration.agent.okhttp.HttpService.call(HttpService.java:97)
      	at com.atlassian.migration.agent.okhttp.HttpService.callJson(HttpService.java:54)
      com.atlassian.migration.agent.service.analytics.AnalyticsSenderService.sendAnalyticsEventBatch(AnalyticsSenderService.java:55)
      com.atlassian.migration.agent.service.analytics.AnalyticsEventConsumer.sendBatchOfEvents(AnalyticsEventConsumer.java:187)
      com.atlassian.migration.agent.service.analytics.AnalyticsEventConsumer.lambda$submitEvents$0(AnalyticsEventConsumer.java:153)
      com.atlassian.migration.agent.store.jpa.impl.DefaultPluginTransactionTemplate.on(DefaultPluginTransactionTemplate.java:40)
      com.atlassian.migration.agent.store.tx.PluginTransactionTemplate.write(PluginTransactionTemplate.java:24)
      com.atlassian.migration.agent.service.analytics.AnalyticsEventConsumer.submitEvents(AnalyticsEventConsumer.java:153)
      com.atlassian.migration.agent.service.analytics.AnalyticsEventConsumer.runJob(AnalyticsEventConsumer.java:135)
      com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.doRunJob(JobRunnerWrapper.java:135)
      com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.lambda$runJob$0(JobRunnerWrapper.java:91)
      com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContextInternal(VCacheRequestContextManager.java:87)
      com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContext(VCacheRequestContextManager.java:71)
      com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.runJob(JobRunnerWrapper.java:91)
      	at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134)
      com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106)
      	at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90)
      com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443)
      com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:438)
      com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:462)
      com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:390)
      com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285)
      com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282)
      com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)
      com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)
      com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34) at java.lang.Thread.run(Thread.java:748)
      

      Workaround

      Please, contact support for further instructions. In some cases, Restore the Confluence Cloud Migration Assistant to the default version can solve this issue.

      Attachments

        Activity

          People

            Unassigned Unassigned
            dbrito Daniel Brito [Atlassian]
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: