How set autocommit=false with container transactions?

Question

Hi all!
A'm using EJB's with transaction attribute=Container.
This is simple scenario:
call Session Bean
begin transaction
call EntityBean1 {
database update 1
call EntityBean2 {
database update 2
end transaction
return from session bean
The problem is:
when update2 fails update1 not rolling back.
A know, that solution of this problem is set AUTOCOMMIT=FALSE in Connection, but how do this with container transactions? Point me exactly to place, where this can be done, if this possible. Or may be no general solution (I.e. Each case demands it's own approach.)?
(I can't directly call method of Connection object because of transaction managed by container)
Tnx a lot.

Answer 1

Hi there,
I have the same problem with Orion and NuSphere MySql.
When I define a container-managed transaction, the autocommit mode is not changed.
I have a session bean for which I set the transaction attribute to REQUIRED and two entity beans for which the transaction attribute is SUPPORTS in the ejbjar.xml file.
The session beans calls the two entity beans and makes some modifications on them like for instance removing them from the database.
When I check whether a transaction can be rolled back, for instance by putting in my code a loop that never ends and then stopping the server, it seems my application is running in autocommit mode. No rollback is done.
This is very strange.
The two entity beans are stored using gemini tables which permit rollbacks. So when I start a transaction inside mySql using sql statements, I can do a rollback without problem.
Any idea of what's going wrong ?
Dimitri.