|
From: Troy M. <Tro...@ho...> - 2004-01-20 23:50:19
|
Note: I posted this to springframework forum as well since it is = applicable to both. The springframework is an open source IoC MVC framework. It also allows = you to incorportate Hibernate framework, easily, for the model side of = things. http://www.springframework.org/docs/reference/index.html As far as my question below. I am not familiar with the SHUTDOWN. How = would I do that? But as far as with the Spring Framework. I don't really have control of = that as far as I know. The framework is locking the database at server = startup, because I have HSQLDB datasource in my application-context.xml. ----- Original Message -----=20 From: fredt=20 To: Troy McKinnon ; hsq...@li...=20 Sent: Tuesday, January 20, 2004 3:31 PM Subject: Re: [Hsqldb-developers] HSQLDB.lck file issues As far as HSQLDB is concerned, an in-process or server instance that = opens a database, creates the *.lck file and does not release it until = the SHUTDOWN command has been issued on the database. You should aim at = incorporating the SHUTDOWN into your framework when you no longer need = the connection to that particular database. If you are using SHUTDOWN and it does not release the *.lck then = please let us know. I don't know about the Sprint framework (reference = please). Please subscribe to the hsqldb-developers if you want to post messages = here. Fred ----- Original Message -----=20 From: Troy McKinnon=20 To: fredt ; hsq...@li...=20 Sent: 20 January 2004 23:11 Subject: Re: [Hsqldb-developers] HSQLDB.lck file issues My issue is basically this... I am using the FILE version of HSQLDB to access CVS files so I can = import them into my (Oracle /or/ Postgres) database. I manually create these files with one process and using the HSQL = driver and Hibernate to access the data and take care of all the Dirty = Work for me. Works very well stand alone. But when I tried to incorporate it = into my Tomcat/Spring/Hibernate framework, it just locks up = (HSQLDB.lck). I discovered this is because I created a HSQLHibernateSessionFactory = bean using the HSQLDataSource in my application-context.xml. On startup Spring must load these and lock them. It doesn't release = them again until tomcat is terminated. I removed the references from my application-context.xml and used a = straight forward hibernate-HSQLDB.cfg.xml file configuration. Basically = skipped spring all together.. and it works fine. I would like to utilize the spring framework.. is there a better way = to do this? I don't want to run SERVER mode on HSQL since they are = basically only temporary import and export files. What would you suggest? Cheers Troy ----- Original Message -----=20 From: fredt=20 To: Troy McKinnon ; hsq...@li...=20 Cc: Troy McKinnon=20 Sent: Tuesday, January 20, 2004 3:02 PM Subject: Re: [Hsqldb-developers] HSQLDB.lck file issues The .lck file prevents two processes from simultaneously opening = the database file. It stays there until you shutdown the database. If = it is causing a problem, please state what it is. Fred ----- Original Message -----=20 From: Troy McKinnon=20 To: hsq...@li...=20 Cc: Troy McKinnon=20 Sent: 20 January 2004 22:12 Subject: [Hsqldb-developers] HSQLDB.lck file issues I am having trouble using HSQLDB using CSV type files. Running = it in tomcat using Hibernate... as soon as the context starts up the = lock file appears and it doesn't ever go away. What exactly creates the = lck file and how can I get by it? Troy |