JPA transaction rollback fails with call to stateless bean

[Jochem Pim]

Inside an UserTransaction I call a method on another stateless EJB. When I rollback this transaction, the entity created in the EJB method is not rolled back. I use EJB 3.1 with JPA 2.0. The transaction begins in doTheTransaction():

    @Stateless
    @LocalBean
    @TransactionManagement(TransactionManagementType.BEAN)
    public class TaskExecutor {

        @Inject private SomeEntityFacade someEntityEJB;
        @Inject private RandomEJB randomEJB;
        @Resource private UserTransaction ut;

        @Asynchronous
        public Future<String> doTheTransaction () { // we start here

            try {
                SomeEntity someEntity = new SomeEntity();
                someEntityEJB.create(someEntity); // this entity is rolled back
                
                // call another EJB to create a SomeEntity, this entity is not rolled back
                randomEJB.createSomeEntity();
                
                // cause error for test
                int i = 5 / 0;

                ut.commit();
            } catch (java.lang.ArithmeticException e) {
                ut.rollback();
            }
        }
        // Omitted exceptions thrown by UserTransaction methods because they give no problems
    }

The RandomEJB:

    @Stateless
    @LocalBean
    @TransactionManagement(TransactionManagementType.BEAN)
    public class RandomEJB {

        @Inject private SomeEntityFacade someEntityEJB;

        public void createSomeEntity () {
            // same code to create entity as in TaskExecutor:
            SomeEntity someEntity = new SomeEntity();
            someEntityEJB.create(someEntity);
        }
    }

To be complete, here is the essential part of SomeEntity:

    @Stateless
    @LocalBean
    public class SomeEntityFacade {

        @PersistenceContext(unitName = "com.mysite.PU")
        private EntityManager em;

        public void create (SomeEntity p_someEntity) {
            em.persist(p_someEntity);
        }

If you are interested, this is my persistence.xml:

    <?xml version="1.0" encoding="UTF-8"?>
    <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
        <persistence-unit name="com.mysite.PU" transaction-type="JTA">
        <jta-data-source>jdbc/myDatabase</jta-data-source>
        <properties></properties>
        </persistence-unit>
    </persistence>

Why is the entity created in RandomEJB not rollback, while the entity created directly inside the transaction is?

[Hebert Coelho]

I was reading a book yesterday and it says that when you use this @TransactionManagement(TransactionManagementType.BEAN) , your transaction is not propagated, even if you rollback, when you call the other EJB, it will suspend your transaction and start a new one.

I think that is what is happening here.

[Jochem Pim]

Hebert Coelho wrote:I was reading a book yesterday and it says that when you use this @TransactionManagement(TransactionManagementType.BEAN) , your transaction is not propagated, even if you rollback, when you call the other EJB, it will suspend your transaction and start a new one.

I think that is what is happening here.

You are right. Removing this:

@TransactionManagement(TransactionManagementType.BEAN)

from RandomRJB resolves the problem.

[lokesh sree]

Hi,

I was reading a book yesterday and it says that when you use this @TransactionManagement(TransactionManagementType.BEAN) , your transaction is not propagated

Even, I was looking at the specs and searching around in the internet regarding this tx propagation. However, I could not find any such clear information. Can you please let us know which book you are referring to?

Thanks,

[Hebert Coelho]

lokesh chenta wrote:Hi,

I was reading a book yesterday and it says that when you use this @TransactionManagement(TransactionManagementType.BEAN) , your transaction is not propagated

Even, I was looking at the specs and searching around in the internet regarding this tx propagation. However, I could not find any such clear information. Can you please let us know which book you are referring to?

Thanks,

Sure, It is the Pro EJB 3, Mike Keith and Merrick Schinca, Page 58

[lokesh sree]

Thanks for the effort Hebert. I actually didnt understand the complete scenario. And was looking at only calls to beans with CMT from inside a BMT bean.

[Hebert Coelho]

In the case of this post, it is using a @TransactionManagement(TransactionManagementType.BEAN).

If it calls another beans the current transaction will be suspended and another one will exists.

I believe that the same rules applies to BMT calling CMT.

Because, in the case of this post, the user has a committed entity and a rollback action that is not working.

That is why I believe that this rule is being applied to BMT calling CMT.

[Hebert Coelho]

I found this book on google books. It is free to access if you want. Chapter 3 talks about t
http://books.google.com.br/books?id=fVCuB_Xq3pAC&pg=PA35&hl=pt-BR&source=gbs_toc_r&cad=4#v=onepage&q&f=false

[Ram Narayan.M]

Hebert,

BMT method to CMT method behaves differenly based on TransactionAttributes used,

Required-->bean transaction will be carried over to CMT managed method since transactional context is available, if not, it will create newly
RequiredNew--> always create new transaction. So, here BMT is suspended and cannot keep the track of "RequiredNew" method
Mandatory--> same as "Required" scenario...if no transactional context i.e., calling this type method without no transaction in line, exception will be thrown

Likewise, it varies for Supported, NotSupported and Never


In turn, CMT to BMT,

CM Transaction will be suspended and BMT method will be invoked without any transactional context. So, BM transactions will be within the business logic code boundary...
So, committed BM Transaction cannot be rolled back when doing Rollback of CMT since CMT does not have the trace of transactions made in BMT managed method.