Hey,

I use Hibernate (with EJB3 annotations)
I have a method that is executed for a long time and execute sort of an Action (an entity)

I would like to manage status of the action, so before execution, I change the Action.status to 'RUNNING', then I invoke em.flush() in order to commit the status first before the long running method execution phase.


So the code looks like:




I can see the query in the log file after em.flush is invoked but the change does not happen on the DB.


With Mysql, it works fine, the problem only happen with Oracle, (maybe there's a need somewhere to do a commit?)


Any ideas?


Thanks in advanced,


Asaf.
[/code]

I think you are right, you have to commit your transaction.
I don't know what kind of Transaction API you use (JTA?) but you could try to call em.getTransaction().begin() before and em.getTransaction().commit() after your statement.

Hey,
Thanks for answering,

I wonder why the behavior is different between the two DB types (Mysql/Oracle) any idea?


Yes, I am using JTA, I'm not too famliar with the behavior, but is it possible to start an inner transaction inside current one that JTA created and then commit the inner one only?, then return back to the original transaction?

I don't want to disturb the standard behavior as the invocations that occur after the status update are very long and complicated, thus I don't want to mange the transaction myself, only for the update.


Thanks,

Asaf.

What kind of table type are you using with MySQL? I would guess that you are using MyISAM tables (the default for MySQL). This table type doesn't support transactions and it doesn't matter if you commit() or not. Instead, you should use the InnoDb table type which support transactions. You should also configure Hibernate to use the MySQL5InnoDBDialect.