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

JCMA migration fails with a migration workflow timed out

XMLWordPrintable

    • 8
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary

      During a migration containing multiple large projects, JCMA may experience an error on project import:

      A step of migration workflow timed out
      

      Many of the projects will be completed successfully, but there may be 1 or more that fail with the same message. In some cases the progress may actually show 100%.

      The same projects that failed, will succeed if the user retries to migrate them individually.

      Workaround

      JCMA 1.9.8 and later releases offer the ability to customize timeout values using JVM arguments, as illustrated below.

      • jcma.request.timeout - timeout for obtaining a connection from the connection manager (Default=20)
      • jcma.socket.timeout - maximum period between two consecutive data packets (Default=20  for JCMA < 1.10.2, and Default=40 for JCMA>=1.10.2)
      • jcma.connect.timeout - timeout until the connection is established (Default=20)

      For LINUX:  Add these values into the file setenv.sh and restart Jira:

      export JVM_SUPPORT_RECOMMENDED_ARGS="-Djcma.request.timeout=120 -Djcma.socket.timeout=120 -Djcma.connect.timeout=120"

      For Windows: Add these values into the file setenv.bat and restart Jira:

      set JVM_SUPPORT_RECOMMENDED_ARGS="-Djcma.request.timeout=120 -Djcma.socket.timeout=120 -Djcma.connect.timeout=120"

      If the parameter "JVM_SUPPORT_RECOMMENDED_ARGS" exists on setenv.sh/setenv.bat, make sure to keep the existing parameters while adding the ones above.

      Suggestion

      The migration appears to fail because of a timeout executing a particular JCMA step such as generating the Post Migration Report.

      Option 1

      To resolve the issue, JCMA's default value of 20 should be increased to 120 as the default. This way the user is less likely to run into this problem.

      Option 2

      The error message "A step of migration workflow timed out" should be updated to include the recommendation of adding the JVM arguments.

      Option 3

      If the project import step was successful and the error was isolated to the Post Migration Report, the logging should be more specific and the migration plan should be completed successfully rather than show a timeout.

            Unassigned Unassigned
            asalinasii@atlassian.com Alfonso S.
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: