JDBCStoreManager.releaseConnection causes rollback???

Question

I thought that getting the SQL connection from PersisientManager would allow
me to do
JDBC stuff on the same connection and in the same transaction. But I cannot
get SQL updates
to 'persist' without calling commit on the transaction.
Is this a bug, user error, or as designed. If any oh the last two, how
can I do db updates through JDBC and have them being tied to the same
transaction as the PM's transaction (and commit when it commits)?
Below is a test program where I expected the number of rows returned to be
1, but
it returns zero.
Thanks,
Eivind Skildheim
Motive Communications, Inc
import java.io.File;
import java.io.FileInputStream;
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Properties;
import javax.jdo.JDOHelper;
import javax.jdo.PersistenceManager;
import javax.jdo.PersistenceManagerFactory;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager;
import com.solarmetric.kodo.runtime.PersistenceManagerImpl;
public class KodoTest
public static void main(String[] args)
try
Properties props = new Properties();
props.load(new FileInputStream(args[0]));
PersistenceManagerFactory pmf =
JDOHelper.getPersistenceManagerFactory (props);
PersistenceManager pm = pmf.getPersistenceManager();
pm.currentTransaction().begin();
JDBCStoreManager sm = getStoreManager(pm);
Connection conn = sm.getConnection();
Statement stmt = conn.createStatement();
stmt.executeUpdate("create table foo(bar number not null)");
stmt.executeUpdate("insert into foo(bar) values(1)");
sm.releaseConnection(conn);
conn = sm.getConnection();
stmt = conn.createStatement();
ResultSet row = stmt.executeQuery("select count(*) from foo");
row.next();
getLogger().info("Number of rows = " + row.getInt(1));
sm.releaseConnection(conn);
System.exit(0);
catch(Throwable e)
getLogger().error("", e);
System.exit(1);
private static JDBCStoreManager getStoreManager(PersistenceManager pm)
return (JDBCStoreManager)
((PersistenceManagerImpl)pm).getStoreManager();
private static Log getLogger()
return LogFactory.getLog(KodoTest.class);

Answer 1

Eivind-
This is as designed: the PersistenceManager allocates Connections on an
as-needed basis, so obtaining a connection from it will not be part of
the PersistenceManager's transaction process.
Instead, what you can do is to use the SQLExecutionListener interface
to execute some SQL in the beforeCommit() phase. E.g., you can do:
     JDBCStoreManager sm = (JDBCStoreManager)myPersistenceManager
          .getStoreManager ();
     SQLExecutionListener listener = new AbstractSQLExecutionListener ()
          public void beforeCommit (SQLExecutionEvent event, Connection c)
               c.createStatement ().executeUpdate ("DO SOME SQL STUFF BEFORE COMMIT");
     sm.addSQLExecutionListener (listener);
See the API at:
http://www.solarmetric.com/docs/latest/docs/javadoc/com/solarmetric/kodo/impl/jdbc/SQLExecutionListener.html
In article <[email protected]>, Eivind Skildheim wrote:
I thought that getting the SQL connection from PersisientManager would allow
me to do
JDBC stuff on the same connection and in the same transaction. But I cannot
get SQL updates
to 'persist' without calling commit on the transaction.
Is this a bug, user error, or as designed. If any oh the last two, how
can I do db updates through JDBC and have them being tied to the same
transaction as the PM's transaction (and commit when it commits)?
Below is a test program where I expected the number of rows returned to be
1, but
it returns zero.
Thanks,
Eivind Skildheim
Motive Communications, Inc
import java.io.File;
import java.io.FileInputStream;
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Properties;
import javax.jdo.JDOHelper;
import javax.jdo.PersistenceManager;
import javax.jdo.PersistenceManagerFactory;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager;
import com.solarmetric.kodo.runtime.PersistenceManagerImpl;
public class KodoTest
public static void main(String[] args)
try
Properties props = new Properties();
props.load(new FileInputStream(args[0]));
PersistenceManagerFactory pmf =
JDOHelper.getPersistenceManagerFactory (props);
PersistenceManager pm = pmf.getPersistenceManager();
pm.currentTransaction().begin();
JDBCStoreManager sm = getStoreManager(pm);
Connection conn = sm.getConnection();
Statement stmt = conn.createStatement();
stmt.executeUpdate("create table foo(bar number not null)");
stmt.executeUpdate("insert into foo(bar) values(1)");
sm.releaseConnection(conn);
conn = sm.getConnection();
stmt = conn.createStatement();
ResultSet row = stmt.executeQuery("select count(*) from foo");
row.next();
getLogger().info("Number of rows = " + row.getInt(1));
sm.releaseConnection(conn);
System.exit(0);
catch(Throwable e)
getLogger().error("", e);
System.exit(1);
private static JDBCStoreManager getStoreManager(PersistenceManager pm)
return (JDBCStoreManager)
((PersistenceManagerImpl)pm).getStoreManager();
private static Log getLogger()
return LogFactory.getLog(KodoTest.class);
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com