Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-60949

Confluence 7.11 EAP development instance keeps throwing "Failed to update database schema" caused by migration assistant app

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Server - EAP
    • Labels:
      None
    • Feedback Policy:
      We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Description

      1. Run a development instance of Confluence 7.11.0-rc1 (using any maven or "atlas-run", "atlas-debug" command)
      2. After startup of the server the attached entries in the logs will keep appearing
      3.  After a while this will also affect performance and cause Java timeout errors (making our integration tests to fail)
      4. These entries in the logs will stop appearing only after disabling the Atlassian Migration Assistant app (com.atlassian.migration.agent)

       

      Logs

      2021-01-18 04:28:10,365 ERROR [Caesium-1-2] [migration.agent.queue.QueueBroker] error An error occurred when getting the next batch for consumer type: DATA_UPLOAD. Message: javax.persistence.PersistenceException: Failed to update database schema
      ....
      Caused by: javax.persistence.PersistenceException: Failed to update database schema
      .....
      Caused by: liquibase.exception.MigrationFailedException: Migration failed for change set META-INF/db-changelog/9-remove-schedule-columns.xml::9-remove-schedule-columns::MPT:
      Reason: liquibase.exception.DatabaseException: Column "SCHEDULEDATE" not found; SQL statement:  ALTER TABLE PUBLIC.MIG_PLAN DROP COLUMN scheduleDate [42122-200] [Failed SQL: ALTER TABLE PUBLIC.MIG_PLAN DROP COLUMN scheduleDate]

       

       

      This errors keep appearing until the migration app is disabled/uninstalled. 

      Is there a way to us the Atlassian SDK commands disabling the migration app before or right after the Confluence instance starts?

       

      This error was not taking place with previous Confluence versions.

        Attachments

          Activity

            People

            Assignee:
            hrehioui Hasnae
            Reporter:
            pablo49 Pablo Gallego
            Votes:
            23 Vote for this issue
            Watchers:
            9 Start watching this issue

              Dates

              Created:
              Updated: