How are you accessing Derby from the terminal? You mentioned that you are using IJ but are you opening an embedded connection to Derby or a client-server one?
If one instance (a separate JVM process such as Tomcat) has already booted Derby, this last one will only be accessible in client-server mode from another JVM instance (terminal window running IJ for instance) using Derby's client network JDBC driver. Cheers --francois On Tue, Apr 21, 2009 at 1:38 PM, mattgaunt <[email protected]> wrote: > > Yeah all of this is done from the same user account, although I think it is > tomcat accessing the database which is preventing the terminal from gaining > access, deleting the .lck files and restarting my computer gives me access > to database again through the terminal ij. > > Guess it's just something I'll have to deal with until the website has > adequit tools to edit the database. > > Thanks for the reply Dag > > > > Dag H. Wanvik wrote: > > > > mattgaunt <[email protected]> writes: > > > >> on database directory /home/matt/Sites/databases/wheretododb in READ > ONLY > > > > Did you verify that the user account running the web server (if > > embedded Derby) or Derby server (if using client/server Derby) has > > write and execute access to /home/matt/Sites/databases/wheretododb > > (if it is a different user than the one who did the ij creation)? > > > > To verify, you could connect to Derby from the same account as holds > > the Web/Derby server with ij and see if you can perform modifications. > > > > Once you perform a clean shutdown of Derby the should be no lock files > > around. They are there to prevent more than one JVM booting Derby at > > the same time. Their presence is usually an indication that a) a JVM > > is running that has booted Derby, or b) such a JVM has crashed or > > stopped without shutting down Derby. You can remove manually them if > > no JVM is running. > > > > Dag > > > > > >> mode > >> > >> Database Class Loader started - derby.database.classpath='' > >> > >> Which is how I know it's in read only mode and there are db.lck dbex.lck > >> files in the database directory. > >> > >> Im new to all this so please be gentle, any help would be great > >> > >> > >> -- > >> View this message in context: > >> > http://www.nabble.com/Derby-on-Tomcat-server-keeps-setting-itself-to-read-only-tp23152838p23152838.html > >> Sent from the Apache Derby Users mailing list archive at Nabble.com. > >> > > > > > > -- > View this message in context: > http://www.nabble.com/Derby-on-Tomcat-server-keeps-setting-itself-to-read-only-tp23152838p23164499.html > Sent from the Apache Derby Users mailing list archive at Nabble.com. > >
