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.

Reply via email to