[kepler-users] problem with HSQL cache

[ben leinfelder]

Rick,
The path is specified in DBConnectionFactory but should probably be  
moved into the config.xml file so that it is more readily changed.
I'm fearful that simply changing the HSQL database path will not be a  
viable option as there are many other cache-specific files in the  
~/.kepler directory that may interfere with this mix of old and new  
databases/cache files.
Certainly give it a try (strongly recommend backing up your  
existing .kepler beforehand) to see if you have satisfactory results.
You might be happier running the different Kepler versions as a  
different user on the same computer - that will allow you to keep the  
~/.kepler directories distinct since they will be under different user  
directories.
-ben

On Aug 25, 2009, at 10:33 AM, Rick Moore wrote:

> Thanks for the prompt response Ben.
>
> This seems to indicate that the path to the HSQL database is  
> hardcoded somewhere in the Kepler src base. If that is the case,  
> would someone please help me find where that is ? I haven't had any  
> luck with cygwin/grep or Windows file search.
>
> I need to be able to run both the prod and dev instances on a daily  
> basis. The prod version to run/maintain existing workflows and the  
> dev version to build/debug new actors. We will eventually go to the  
> newest source base for both,  but that may take a couple of months.
>
> Rick
>
> ben leinfelder wrote:
>> Rick,
>> Unfortunately we do not currently have an "upgrade" approach for  
>> going from Kepler 1.0 to the development trunk (though it is  
>> something we are attempting to support in the future).
>> To preserve your existing HSQL database (say, if you plan on using  
>> Kepler 1.0 again after you successfully run Kepler from the trunk)  
>> I'd recommend copying your ~/.kepler directory to a safe location  
>> and then re-running Kepler from the trunk. There have been  
>> substantial changes to the cache database (the HSQL version was  
>> upgraded and various tables have had their schema altered). Your  
>> new ~/.kepler (automatically created when you launch Kepler from  
>> the trunk) will allow you to use the trunk version. If/when you  
>> want to go back to Kepler 1.0, you'll need to swap in your old  
>> ~/.kepler and launch 1.0.
>> Thanks,
>> -ben
>>
>> On Aug 25, 2009, at 9:38 AM, Rick Moore wrote:
>>
>>> I just tried to run Kepler 1.0.0 and it failed. This extract from  
>>> the stack trace suggests that the problem is a corrupt HSQL  
>>> database.
>>>
>>> java.sql.SQLException: Wrong database file version
>>>  at org.hsqldb.jdbc.jdbcUtil.sqlException(Unknown Source)
>>>  at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
>>>  at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
>>>  at org.hsqldb.jdbcDriver.connect(Unknown Source)
>>>
>>> I think this happened because I recently downloaded and built  
>>> Kepler from the dev tree and it stomped on my production database.
>>>
>>> Is there any way to tell one of these instances to look for the  
>>> HSQL database in a different location than my home directory ?
>>>
>>> Thanks,
>>>
>>> Rick Moore
>>> Content Management Specialist
>>> Information Science
>>> Cornell University
>>> email: rem63 at cornell dot edu
>>>
>>> "Once in a while you will be shown the light in the strangest of  
>>> places, if you look at it right"
>>> from Scarlet Begonias by the Grateful Dead
>>> _______________________________________________
>>> Kepler-users mailing list
>>> Kepler-users at kepler-project.org
>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users