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

Confluence startup fails if using an HSQL database from JNDI, or with a manually defined connection string

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 4.2
    • None
    • None

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Confluence seems to assume that if you're using an HSQL database, it must be a file based database located at CONFLUENCE_HOME/database/confluencedb. So, if you're using a JNDI supplied HSQL database, or using an in memory database (eg jdbc:hsqldb:mem:confluence), or using HSQL as a server (eg jdbc:hsqldb:hsql://localhost/confluence, very useful if you actually want to connect to the database externally and browse it while Confluence is still running), or simply pointing it at some other file location, then Confluence fails to startup with the following error:

      2010-09-03 13:39:06,978 ERROR [main] [atlassian.confluence.setup.ConfluenceConfigurationListener] contextInitialized An error was encountered while bootstrapping Confluence (see below): 
      java.io.FileNotFoundException: /home/jroper/src/atlassian/studio/branches/initialdata/studio-fireball/target/home/confluence-home/database/confluencedb.properties (No such file or directory)
      java.lang.RuntimeException: java.io.FileNotFoundException: /home/jroper/src/atlassian/studio/branches/initialdata/studio-fireball/target/home/confluence-home/database/confluencedb.properties (No such file or directory)
      	at com.atlassian.confluence.setup.DefaultBootstrapManager.upgradeHSQL(DefaultBootstrapManager.java:226)
      	at com.atlassian.confluence.setup.DefaultBootstrapManager.performPersistenceUpgrade(DefaultBootstrapManager.java:176)
      	at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.init(DefaultAtlassianBootstrapManager.java:76)
      	at com.atlassian.config.util.BootstrapUtils.init(BootstrapUtils.java:35)
      	at com.atlassian.confluence.setup.ConfluenceConfigurationListener.initialiseBootstrapContext(ConfluenceConfigurationListener.java:76)
      	at com.atlassian.confluence.setup.ConfluenceConfigurationListener.contextInitialized(ConfluenceConfigurationListener.java:40)
      	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3934)
      	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4429)
      	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
      	at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
      	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
      	at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
      	at org.apache.catalina.core.StandardService.start(StandardService.java:516)
      	at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
      	at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
      	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
      Caused by: java.io.FileNotFoundException: /home/jroper/src/atlassian/studio/branches/initialdata/studio-fireball/target/home/confluence-home/database/confluencedb.properties (No such file or directory)
      	at java.io.FileInputStream.open(Native Method)
      	at java.io.FileInputStream.<init>(FileInputStream.java:106)
      	at com.atlassian.confluence.setup.DefaultBootstrapManager.upgradeHSQL(DefaultBootstrapManager.java:223)
      	... 20 more
      

            [CONFSERVER-20739] Confluence startup fails if using an HSQL database from JNDI, or with a manually defined connection string

            Caused by the code for upgrading HSQLDB 1.7 to 1.8.

            Fixed by cmiller by removing all the old upgrade tasks and related code (the HSQLDB upgrade was long before Confluence 2.7.4).

            Richard Atkins added a comment - Caused by the code for upgrading HSQLDB 1.7 to 1.8. Fixed by cmiller by removing all the old upgrade tasks and related code (the HSQLDB upgrade was long before Confluence 2.7.4).

            Joe Clark added a comment -

            Flagging as a potential devspeed improvement. Value for customers is low, but value for Confluence developers is high.

            Joe Clark added a comment - Flagging as a potential devspeed improvement. Value for customers is low, but value for Confluence developers is high.

              Unassigned Unassigned
              jroper James Roper [Atlassian]
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: