db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pasi Paasiala" <pasi.paasi...@solibri.com>
Subject how to get rid of the derby.rawStoreDaemon thread
Date Wed, 03 Feb 2010 12:48:55 GMT
We are evaluating derby to use it for storing additional information related
to our models (Java objects).

When we save our model, we save the database files and folders with it. The
only way that we have found to ensure that the database files are in a
consistent state is to close the connection before getting a snapshot of the
files and then start the database again. Is there another way of finding out
if all data is stored in the files?

Another problem is that when we save a model and open another one, we close
the database and open another one. In that case we get another instance of
derby.rawStoreDaemon thread. Why doesn't the first derby.rawStoreDaemon shut
down even though we call Connection.close()? The only way that we have found
to shut down the thread is by calling:

	Monitor.getMonitor().shutdown();

However, if we call that, we get the following exception the next time we
try to make a connection:

java.sql.SQLException: org.apache.derby.jdbc.EmbeddedDriver is not
registered with the JDBC driver manager
	at org.apache.derby.jdbc.AutoloadedDriver.getDriverModule(Unknown
Source)
	at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)
	at java.sql.DriverManager.getConnection(DriverManager.java:582)
	at java.sql.DriverManager.getConnection(DriverManager.java:207)

Someone else had had a similar kind of problem:
http://osdir.com/ml/derby-user-db-apache/2009-05/msg00027.html

Regards,

Pasi


Mime
View raw message