com.atlassian.stash.internal.migration.MigrationException

One or more database connections were not closed within the allotted timeout. To prevent corruption due to inconsistent state, the migration has been aborted. Please try your migration again when the system is under less load.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web2

  • via Atlassian JIRA by Thomas Bright [Atlassian], 1 year ago
    One or more database connections were not closed within the allotted timeout. To prevent corruption due to inconsistent state, the migration has been aborted. Please try your migration again when the system is under less load.
  • via Atlassian JIRA by Thomas Bright [Atlassian], 11 months ago
    One or more database connections were not closed within the allotted timeout. To prevent corruption due to inconsistent state, the migration has been aborted. Please try your migration again when the system is under less load.
  • Stack trace

    • com.atlassian.stash.internal.migration.MigrationException: One or more database connections were not closed within the allotted timeout. To prevent corruption due to inconsistent state, the migration has been aborted. Please try your migration again when the system is under less load. at com.atlassian.stash.internal.migration.DefaultMigrationService.drainDataSource(DefaultMigrationService.java:603)[stash-service-impl-1.3.0-SNAPSHOT.jar:na] at com.atlassian.stash.internal.migration.DefaultMigrationService.writeBackup(DefaultMigrationService.java:388)[stash-service-impl-1.3.0-SNAPSHOT.jar:na] at com.atlassian.stash.internal.backup.AbstractBackupSupport.backup(AbstractBackupSupport.java:92)[stash-service-impl-1.3.0-SNAPSHOT.jar:na] at com.atlassian.stash.internal.migration.DefaultMigrationService.performMigration(DefaultMigrationService.java:714)[stash-service-impl-1.3.0-SNAPSHOT.jar:na] at com.atlassian.stash.internal.migration.DefaultMigrationService.access$100(DefaultMigrationService.java:63)[stash-service-impl-1.3.0-SNAPSHOT.jar:na] at com.atlassian.stash.internal.migration.DefaultMigrationService$1.run(DefaultMigrationService.java:166)[stash-service-impl-1.3.0-SNAPSHOT.jar:na] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)[na:1.6.0_33] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)[na:1.6.0_33] at java.util.concurrent.FutureTask.run(FutureTask.java:138)[na:1.6.0_33] at com.atlassian.stash.internal.concurrent.StateTransferringExecutor$StateTransferringRunnable.run(StateTransferringExecutor.java:68)[stash-platform-1.3.0-SNAPSHOT.jar:na] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)[na:1.6.0_33] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)[na:1.6.0_33] at java.util.concurrent.FutureTask.run(FutureTask.java:138)[na:1.6.0_33] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)[na:1.6.0_33] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)[na:1.6.0_33] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[na:1.6.0_33] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[na:1.6.0_33] at java.lang.Thread.run(Thread.java:662)[na:1.6.0_33]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.