Hi Kevin, Thanks for the reply. Yes, it does work with Postgresql, the caching problems don't seem to be an issue in there. I did notice there is a "WRITE_WAIT" time that is setup. I see it go across when the server starts up, basically I think it only 'writes' (I would really call it a flush) to the files once every 10 seconds. I tried to figure out how to adjust that record to not wait and do the writes immediately, but those seem to be only posted via SQL in HSQL 1.8. HSQL 1.9 is supposed to support adjustments of those values on the jdbcURL line, but when I tried 1.9RC6 there were lots of errors that came across on a byte[] column... I added a shutdownhook to my app that does a Thread.sleep(10 * 1000) (10 seconds), and the data always gets flushed out. This is a hack I really can't leave in there for very long... It really seems like there should be a good reliable way for me to shutdown the db when the app shuts down but I have not found it yet.
There are in fact 2 different db instances (schema's? not sure what to call it in HSQL) that I'm using, one is read-only and the other one is the one I'm having issues with, I wonder if this problem is related to having multiple db's open. The tables in the 2 db's are not the same. -chris Kevin Sutter wrote: > > Hi coloradoflyer, > I'm not an expert with hsql, but I don't see anything "wrong" with your > configuration. From your description, your application works just fine > with > PostgreSQL? But, just changing the database configuration to HSQL, then > it > fails? And, there are no errors getting posted? If no errors are being > logged, then my guess is that OpenJPA is (accidentally) writing to a > different database than what you think is configured. > > Have you tried turning on TRACE for openjpa.log? That would show what > database and what tables are being used. This would also show the SQL > that > is being pushed out to the database, along with any errors that might have > occurred. I'd start with that for debugging. > > Good luck, > Kevin > > On Wed, Oct 21, 2009 at 11:28 PM, coloradoflyer > <[email protected]>wrote: > >> >> Hi all, >> >> I'm writing an application that currently runs in both HSQL and >> PostgresQL, >> really it should run in any db, but those 2 are ones I have currently >> tested. >> >> I'm using openejb (Embedded), and openjpa-2.1. The problem is, when I >> run >> against HSQL and I create a new entity (seems like any row for any >> entity), >> then shutdown my application shortly (within a second or 2) after >> creating >> the row, that row never gets persisted or written out to the log or >> script >> file. >> >> The application is a swing app, and I set the main window closing to exit >> the app, I'm assuming this should cause a standard shutdown. >> >> I've looked in the hsql configuration docs and do not seen anything that >> seems to be obvious (to me). This seems to be a basic flush problem, but >> I'm not sure what to change to get things to flush. >> >> I did create a shutdown hook and did a shutdown of openejb, but that did >> not >> fix things. Any help is greatly appreciated >> >> -chris >> >> my openejb config file has the following DataSources created: >> >> <Resource id="myDatabase" type="DataSource"> >> JdbcDriver org.hsqldb.jdbcDriver >> JdbcUrl jdbc:hsqldb:file:db/mydb >> JtaManaged true >> </Resource> >> <Resource id="myDatabaseUnmanaged" type="DataSource"> >> JdbcDriver org.hsqldb.jdbcDriver >> JdbcUrl jdbc:hsqldb:file:db/mydb >> JtaManaged false >> </Resource> >> >> and in my persistence.xml file I have: >> <persistence xmlns="http://java.sun.com/xml/ns/persistence"; >> version="1.0"> >> <persistence-unit name="mydb-unit" transaction-type="JTA"> >> <jta-data-source>myDatabase</jta-data-source> >> <property name="openjpa.Log" value="DefaultLevel=ERROR" /> >> <property name="openjpa.jdbc.SchemaFactory" >> value="native(ForeignKeys=true)"/> >> <property name="openjpa.AutoDetach" value="commit"/> >> <property name="openjpa.RetainState" value="false"/> >> <property name="openjpa.DetachState" value="fetch-groups"/> >> </properties> >> </persistence-unit> >> </persistence> >> >> -- >> View this message in context: >> http://n2.nabble.com/HSQL-update-problem-tp3870187p3870187.html >> Sent from the OpenJPA Users mailing list archive at Nabble.com. >> > > -- View this message in context: http://n2.nabble.com/HSQL-update-problem-tp3870187p3874719.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
