Confluence Documentation

Confluence Latest 
Confluence 5.3 Documentation 
Confluence 5.2 Documentation 
Confluence 5.1 Documentation 
More...
 

 

Search the Confluence Knowledge Base

You're visiting the Confluence Knowledge Base. Visit the Confluence Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata

Symptoms

  1. Confluence uses Microsoft SQL Server.
  2. Confluence cannot start after installing or upgrading some plugins or the newly installed/upgraded plugins are disabled upon startup. Known affected plugins:
    • Universal Plugin Manager (UPM)
    • Office Connector
    • SharePoint Connector
    • Scroll Office
    • RefinedWiki
    • (New) Code Macro
    • Table Plugin
  3. The following appears in the atlassian-confluence.log:

    In context similar to:

Diagnosis

Take thread dumps of the process every 30 seconds from start-up until after the timeout warnings. If they contain the following, then the Workaround should apply. If not, the thread-dumps should help diagnose the real problem.

Spring executor stack trace  Expand source

Cause

We have not identified the definite cause yet, but this problem happens when some of the plugins ended up waiting to get access to the BANDANA table. The problem is that Microsoft SQL Server is escalating row locks to table locks and thereby blocking access to the table and causing an effective deadlock. This bug is being tackled at CONF-21986.

Workaround

Configure your database to use the recommended isolation level, which is Read Committed with Row Versioning. Please refer to the workaround listed in this KB article for instructions.

Resolution

Upgrade to Confluence 3.5.9 or higher where CONF-21986 has been fixed.

Related Content

CONF-21986

 Expand to see related content
Help us improve!
Is this article helpful?
Is the content complete?
Is it well written?

4 Comments

  1. We've heard from a customer that the following solved the problem on MSSQL:

  2. We also ran into this issue with the following plugins:

    New Code Macro Plugin

    Table Plugin

    We are going to try the fix above and see if it works, since as it is we have been unable to start Confluence after upgrading these plugins (on our dev copy to get ready for live upgrade).

    1. Hi Kristyn,

      I've included those plugins in the KB. If you are still having an issue, please raise a support ticket and we'll help you there. (smile)

      Cheers,
      Husein

  3. I'm getting this kind of error in Confluence 4.3.7  (at least Hercules points me to this KB article)

    The errors are

    ERROR [FelixPackageAdmin] 
    [internal.util.concurrent.RunnableTimedExecution] execute Closing 
    runnable for context 
    NonValidatingOsgiBundleXmlApplicationContext(bundle=org.swift.confluence.table-sorter-plugin, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
    
    ERROR
     [FelixPackageAdmin] [internal.util.concurrent.RunnableTimedExecution] 
    execute Closing runnable for context 
    NonValidatingOsgiBundleXmlApplicationContext(bundle=org.randombits.confluence.metadata, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
    
    

    Should I apply the above SQL, or better contact Swift and Customware support?