Confluence has been updated to ver 6.15.9. In case of any troubles, please contact infra team.



Getting below errors while syncing the issues from Jira cloud to Jira server.

Issue 1 - Unexpected error like the below screenshot. These type of issues are 250 of them.

Issue 2 - License error like the below screenshot. These type of issues are 1000 of them.

How can these issues be fixed. I need help asap as my client is waiting for this syncing.

Below is the zip file of the generated error related to Issue 1 as a sample.


I dont have any zip files related to Issue 2. Because they are not generated.

    CommentAdd your comment...

    1 answer


      The error text shows that there is a licensing error.
      Both sides of the connection need a valid license. 
      If you can get this arranged - you can clear this error

      1. A Bhavya Praneeth

        Thank you for your answer.

        We purchased a license in our cloud Jira instance and now the sync queue is ready to sync.

        But my local server instance is not ready because the license is not purchased there. Why because the local server is also a trail Jira instance for 30 days. We took a trial version for trying the migration process from cloud to server, Once this is successful we won't be using this local server instance because we will export the whole dump to our client because they have the paid version of the on-premise instance.

        As per your suggestion we cannot purchase a Jira server instance for just this one migration.

        Then how would I update my license in the Jira server instance to complete the other 1360 issues to be synced.

        Please suggest the alternative for this.

        Waiting for your reply.

      2. Francis Martens (iDalko)

        I don't understand.
        Why don't you sync with the instance which has the valid license?

      3. A Bhavya Praneeth

        Hi Francis,

        We purchased license on both the instances and I started issues sync process. 79 issues among 1360 were been synced and again unexpected errors are shown. 

        Can you please help me on this asap.

        Below is the stack trace of one of the issue - 

        com.exalate.api.exception.bug.BugException: Unexpected error occurred. Generate an exalate file and contact support. at at$$anonfun$1.applyOrElse(EventProcessorService.scala:143) at$$anonfun$1.applyOrElse(EventProcessorService.scala:136) at scala.concurrent.Future.$anonfun$recoverWith$1(Future.scala:417) at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:41) at at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:56) at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:93) at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$ at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:85) at akka.dispatch.BatchingExecutor$ at at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:48) at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source) at java.base/java.util.concurrent.ForkJoinPool.scan(Unknown Source) at java.base/java.util.concurrent.ForkJoinPool.runWorker(Unknown Source) at java.base/ Source) Caused by: IO operation was stopped unexpectedly after 251727872 bytes because of No space left on device at$$anon$1.onPush(FileOutputStage.scala:67) at at at at at$SimpleBoundaryEvent.execute(ActorGraphInterpreter.scala:56) at$SimpleBoundaryEvent.execute$(ActorGraphInterpreter.scala:52) at$BatchingActorInputBoundary$OnNext.execute(ActorGraphInterpreter.scala:95) at at$stream$impl$fusing$ActorGraphInterpreter$$processEvent(ActorGraphInterpreter.scala:769) at$$anonfun$receive$1.applyOrElse(ActorGraphInterpreter.scala:784) at at$(Actor.scala:533) at at at at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:270) at at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$ Source) at java.base/ Source) Caused by: No space left on device at java.base/ Method) at java.base/ Source) at java.base/ Source) at java.base/ Source) at java.base/ Source) at$$anon$1.onPush(FileOutputStage.scala:63) ... 20 more

      4. Francis Martens (iDalko)

        Can you raise an issue on our support portal (here) with the exalate support zip added.


      CommentAdd your comment...