Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-61189

Opening the base URL multiple times during Data Center migration will break the migration process.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 7.4.7
    • None

      Issue Summary

      Opening base URL multiple times during Data Center migration will break the migration process.

      Steps to Reproduce

      1. Open multiple tabs to point to the same URL of Confluence.
      2. Install Confluence as Server.
      3. In the Administration > Licensing switch the license to DC license.
      4. Restart Confluence instance
      5. During the startup, confluence will go into the migration process.
      6. After setting up network cluster parameters, you will have few minutes while the migration is still running
      7. Open other tabs and try to open Confluence base URL a few times.

      Expected Results

      Nothing will happen, and you will see a blank page that is trying to load.

      Actual Results

      You will receive error 500 without any stack trace in the browser:

      But from the side of the logs, you will see this error:

      2021-02-11 15:29:10,989 ERROR [http-nio-6747-exec-4] [atlassian.confluence.servlet.ConfluenceServletDispatcher] sendError Could not execute action
       -- url: /c747/setup/finishsetup.action | traceId: 000c8fc8f222e598 | userName: anonymous
      java.lang.NullPointerException
      	at com.atlassian.confluence.setup.actions.FinishSetupAction.execute(FinishSetupAction.java:57)
      	at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:168)
      	at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:35)
      	at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)
      	at com.atlassian.confluence.core.ConfluenceWorkflowInterceptor.intercept(ConfluenceWorkflowInterceptor.java:33)
      	at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)
      	at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:35)
      	at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)
      	at com.atlassian.confluence.security.interceptors.CaptchaInterceptor.intercept(CaptchaInterceptor.java:42)
      	at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)
      ....
      2021-02-11 15:29:11,044 FATAL [http-nio-6747-exec-4] [atlassian.spring.container.SpringContainerContext] getComponent Spring Application context has not been set
       -- traceId: 00efb6ec17e0bf05
      2021-02-11 15:29:11,045 WARN [http-nio-6747-exec-4] [atlassian.confluence.status.SystemErrorInformationLogger] toString No SystemInformationService could be retrieved from the Container.
       -- traceId: 00efb6ec17e0bf05
      
      
      

      Workaround

      Make sure that nothing can reach your Confluence instance at the time, like load balancer health checks from AWS, users, or different tabs that are targeting Confluence instance.
      Changing the server.xml connector port temporarily can also help to finish migration uninterrupted.

              Unassigned Unassigned
              gpaunovic g
              Votes:
              10 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated: