Container Managed Transactions and MySQL/InnoDB

[gseel]

I am trying to add some transaction management to a JBoss 3.2 + MySQL/InnoDB system. The system uses Stateless Session EJBs and purpose written DAOs. All methods of the EJBs have Required option for Transactions.

I have written a test method that does two inserts into a table, the second of which causes an SQLException. The behaviour I want is for the first insert to be rolled back but this doesn't happen.

Could this be because AUTOCOMMIT is turned on by default? If so how do I set things up so that it is not turned on? If not, does anyone have any ideas what else I may have overlooked?

[darranl]

The SQLException that is being thrown is a checked exception that you must be handling within a catch block in your code. This in itself is not enough to cause a transaction to be rolled back.

When you catch the SQLException You can either call setRollbackOnly() on the SessionContext that was passed into your session bean, or you can throw a RuntimeException from the business method of your session bean.

[gseel]

That sorted it. Many thanks.