Large XML Imports in Confluence Data Center Can Fail Due to Hazelcast

XMLWordPrintable

    • 1
    • Severity 2 - Major

      Problem

      When importing large spaces in Confluence, while running multiple nodes, imports can fail with the below error:

      2018-09-23 14:16:34,148 ERROR [Long running task: Importing data] [confluence.importexport.xmlimport.BackupImporter] importEntities Cannot import the entities: 
       -- url: /confluence/admin/restore-local-file.action | referer: http://confluence.test/confluence/admin/backup.action | traceId: 9f715403bc8f9b4c | userName: admin | action: restore-local-file
      com.atlassian.confluence.importexport.ImportExportException: Unable to complete import: Error while importing backup: Current thread is not owner of the lock! -> <not-locked> 
      ...
      Caused by: java.lang.IllegalMonitorStateException: Current thread is not owner of the lock! -> <not-locked>Caused by: java.lang.IllegalMonitorStateException: Current thread is not owner of the lock! -> <not-locked> at com.hazelcast.concurrent.lock.operations.UnlockOperation.ensureUnlocked(UnlockOperation.java:71) at com.hazelcast.concurrent.lock.operations.UnlockOperation.unlock(UnlockOperation.java:65) at com.hazelcast.concurrent.lock.operations.UnlockOperation.run(UnlockOperation.java:57) at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:137) at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:315) at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processPacket(OperationThread.java:142) at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.process(OperationThread.java:115) at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.doRun(OperationThread.java:101) at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.run(OperationThread.java:76) at ------ End remote and begin local stack-trace ------.(Unknown Source)

      Workaround

      Bring down any additional nodes until just 1 node is running.  Run the import.  It should succeed now.

            Assignee:
            Unassigned
            Reporter:
            Jason B (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: