Hibernate version: 3.2.3

session factory configuration:

<session-factory>
<property name="hibernate.connection.driver_class">org.postgresql.Driver</property>
<property name="hibernate.connection.url">jdbc:postgresql://localhost:5432Repository1</property>
<property name="hibernate.connection.isolation">4</property>
<property name="hibernate.dialect">org.hibernate.dialect.PostgreSQLDialect</property>
<property name="hibernate.transaction.factory_class">org.hibernate.transaction.CMTTransactionFactory</property>
<property name="hibernate.connection.autocommit">false</property>
<property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.JBossTransactionManagerLookup</property>
<property name="hibernate.order_updates">false</property>

<property name="hibernate.transaction.auto_close_session">true</property>
<property name="transaction.flush_before_completion">true</property>
<property name="hibernate.jdbc.batch_size">0</property>
<!-- JDBC connection pool (use the built-in) -->
<property name="connection.autoReconnect">true</property>
<property name="connection.autoReconnectForPools">true</property>
<property name="connection.pool_size">5</property>
<property name="idle-timeout-minutes">3</property>

</session-factory>


Mapping documents:


<?xml version="1.0"?>

<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">

<hibernate-mapping>

<class name="TriggerWrapper">
<id name="id" column="primaryKey"/>
<property name="triggerName"/>
</class>

</hibernate-mapping>


Code between sessionFactory.openSession() and session.close():
/*
Start of relevant code.
This code executes in the context of a CMT Session bean
*/

Session hibSess = anHIBSessionFactory.getCurrentSession();

Transaction tx = hibSess.getTransaction();


tx.begin();

TriggerWrapper myObj = new TriggerWrapper("aTest");

hibSess.save(myObj);

tx.commit();

/*
End of relevent code
*/





Database name and version: PostgreSQL 8.2.4


When the above Java code is executed, there isn't a new TriggerWrapper
instance saved to the DB.

What am I doing wrong here.

Thanks in advance.

What is really odd about this is.
When setting the show-sql to true.

I can see the generated insert statements.
However, these statements never make it to the DB.
Because, again, there aren't any new rows that have been inserted.


Another thing to note.
If I run my junit tests more than once without restarting the app-server.
I get a duplicate key exception on the instance I attempt to save.

When I restart the app-server. I can then save the newly created trigger
wrapper instance.

This says to me that there is a problem with the hibernate session instance
not flushing it's contents to the DB.


Anyone care to comment.

The only way I found to persist a an object with 3.2.3ga in a Transaction context
is by setting the "hibernate.connection.autocommit" property to true.


What is up ??

CMT = Container managed Transactions - The container provides the transaction operations on the boundaries (usually a method call). Your code does not appear to compatible with CMT. I would think you need to review what you have done as basically you are not using CMT.

I suggest you read Christians book and the samples from the book for proper transaction management and how to set it up correctly.

Even when I reduced the code to


Which, from what I understand, should have saved and committed instance
myObj to the DB since it executes in the context of a CMT.

But, myObj instance is never saved.

I have seen other posting here in this forum regarding the same problem of Objects NOT being saved, both in the context of using the JTA api and also in the context of CMT,
with no clear cut answer.

This must be a configuration issue, but, where can I find the correct configuration
for session factory in order to use CMT.


Thanks in advance.

[/code]

For my current project (and most previous projects), I am using CMT extensively. The tx boundaries are set via SLSB method signature that a transaction should be started. In the case of JBoss I have used the MBean method (SAR/HAR) for session factory setup. The SLSB setup the the transaction (since its required) a JNDI lookup gets the Session factory thus acces to the session and away we go. All works well. Other than how you getting the Session factory session (and then maybe not depending on what behind that method) the only reason your having any issues is the initial setup/configuration. I suggest you look at some sample code and try again. Alternatively, try non CMT transaction just to make sure you going in the right direction.