Not flushing changes made in current transaction

Question

I encounter a problem that KODO doesn't flush changes made in current
transaction. I'm using an external transaction manager (JOTM) and XA
datasource (xapool). From the console output, I know I have an active
transaction. According to the KODO automatic flush behaviour
(http://solarmetric.com/Software/Documentation/3.1.2/docs/ref_guide_dbsetup_retain.html),
given kodo.FlushBeforeQueries is true and kodo.ConnectionRetainMode is
transaction, flush should happen before query.
The code is something like this:
userTransaction.begin();
String field1 = "abc";
long field2 = 10L;
String field3 = "123";
Foo foo = new Foo(); // Foo's PK is field1, field2 and field3.
foo.setField1(field1);
foo.setField2(field2);
foo.setField3(field3);
foo1(foo);
Collection foos = foo2(field1, field2);
System.out.println("foos.isEmpty()? : " + foos.isEmpty());
userTransaction.commit();
public void foo1(Foo foo)
PersistenceManager pm = null;
try
pm = getPersistenceManager();
System.out.println("PM.TX: " + pm.currentTransaction() + " active:
" + pm.currentTransaction().isActive());
pm.makePersistent(foo);
catch (ResourceException e)
e.printStackTrace();
finally
if (pm != null && !pm.isClosed())
pm.close();
public Collection foo2(String field1, long field2)
PersistenceManager pm = null;
StringBuffer filter = new StringBuffer();
HashMap parameters = new HashMap();
StringBuffer paramList = new StringBuffer();
Extent ex = null;
Query query = null;
Collection result = null;
Collection result1 = new ArrayList();
Long field2Long = new Long(field2);
try
pm = getPersistenceManager();
System.out.println("PM.TX: " + pm.currentTransaction() + " active:
" + pm.currentTransaction().isActive());
ex = pm.getExtent(Foo.class, true);
filter.append("field1 == paramField1");
filter.append(" && field2 == paramField2");
paramList.append("String paramField1");
paramList.append(" , Long paramField2");
parameters.put("paramField1", field1);
parameters.put("paramField2", field2Long);
query = pm.newQuery(ex, filter.toString());
query.declareParameters(paramList.toString());
result = (Collection) query.executeWithMap(parameters);
catch (ResourceException e)
e.printStackTrace();
finally
if (pm != null && !pm.isClosed())
pm.close();
return result;
From the console,
PM.TX: kodo.runtime.PersistenceManagerImpl@b34b1 active: true
PM.TX: kodo.runtime.PersistenceManagerImpl@b34b1 active: true
foos.isEmpty()? true
If the userTransaction is committed before invoking foo2(), then, the Foo
object is created and foos.isEmpty() returns false.
I am using KODO version: 3.1.2. Here is the kodo.properties:
javax.jdo.PersistenceManagerFactoryClass:
kodo.jdbc.runtime.JDBCPersistenceManagerFactory
javax.jdo.option.Optimistic: true
javax.jdo.option.RetainValues: true
javax.jdo.option.NontransactionalRead: true
javax.jdo.option.ConnectionFactoryName: jdbc/datasource
javax.jdo.option.IgnoreCache: false
kodo.Connection2UserName: <some user>
kodo.Connection2Password: <some password>
kodo.Connection2URL: jdbc:oracle:thin:@<some host>:1521:<some db>
kodo.Connection2DriverName: oracle.jdbc.driver.OracleDriver
kodo.jdbc.DataSourceMode: enlisted
kodo.jdbc.ForeignKeyConstraints: true
kodo.FlushBeforeQueries: true
kodo.ConnectionRetainMode: transaction
kodo.jdbc.VerticalQueryMode=base-tables
kodo.TransactionMode: managed
kodo.ManagedRuntime :
invocation(TransactionManagerMethod=foo.TransactionManagerUtil.getTransactionManager)
kodo.jdbc.DBDictionary : oracle(BatchLimit=0)
Any ideas are appreciated.
Regards,
Willie Vu

Answer 1

Abe White wrote:
Do you get the same behavior with local transactions?
I don't see anything immediately wrong with your code, but all our internal
tests are passing, and no other user has reported a problem.In a single transaction, I'm using multiple persistence managers which are
closed after usage (method foo1() and foo2() gets different persistence
managers and close them before return). I don't think I can use local
transactions, can I?