This page last changed on Oct 04, 2005 by jeff.
This problem has been fixed in JIRA 3.3 and above

Symptoms

Occasionally people start JIRA standalone up to find that their database has disappeared, and they are asked to go through the setup wizard again.

Solution

The problem is that the path to the HSQL database (that ships with JIRA standalone) is relative to where you started the application.

So this command:

c:\jira\bin\> startup.bat

Will create a database in a different directory to:

c:\jira\> bin\startup.bat

The solution is to shut down JIRA and start JIRA up from the normal location.

Explanation

HSQL's database location is specified at a relative location. You can see this in server.xml in Tomcat:

<parameter>
<name>url</name>
<value>jdbc:hsqldb:../database/tomcatdb</value
</parameter>

As JIRA does not know where it will be installed, we cannot specify an absolute directory. In Tomcat 4, there is no way to get the TOMCAT_HOME variable from inside the JVM either.

This should be fixed when we upgrade JIRA standalone to Tomcat 5.

Document generated by Confluence on Oct 06, 2009 00:26