Weblogic 8.1, EJB Stateless Session Bean, for transaction marked required, I can only get objects to persist successfully if I do:

session.beginTransaction();
session.save(obj);
session.flush();
tx.commit();

My understanding, from reading several documentation, is that only flush is required and tx.commit() is NOT needed. Any ideas why it will only work if both flush/commit are used? When doing only flush OR commit alone, hibernate successfully creates object with new generated id, but nothing is saved to DB when done with transaction - and no errors are returned.

Thanks in advance for your help.

Are you sure you're closing your session properly?

Yes, I am closing the session properly with session.close().

You've got it backwards, flush() will be called on commit().

From section 12.2.1 of the reference docs:

You don't have to flush() the Session explicitly - the call to commit() automatically triggers the synchronization.

Ok, not sure what I read but it seems that my above post isn't quite the answer you were looking for so you don't quite have it backwards ;)

In your above example, I would expect if you used both flush() and commit() OR if you used commit() the data would be persisted. Are you changing the flush mode on your session?

That is also my understanding, that commit() should take care of persisting without the need to explicitly call flush() since that is what commit() will do.

I also believe that commit() is not necessary since I am already in a transaction managed environment, so if I don't want to use Transactions explicitly, I don't have to, but I found that using flush alone doesn't work for me either.

I am not changing the flush mode, but I will look into that to see if its something related to the problem. My goal is to not have to use both, but one or the other only.

Thanks for the info.