Weblogic 10.0, JTA -JDBC ejb rollback problem

Question

Hi,
I have one statless-session bean, with bean managed transaction.
ejbmethod()
utx=getUserTransaction();
try{
utx.begin();
method1(); //in this i am updating few table in DB -DB connection is taken in the same method and closed there
method2(); // calling a stored procedure to do smthing etc
method3(); //update smthing else
utx.commit();
}catch()
utx.rollback()
the rollback does not happen properly.
The code is not wrong, no nested transaction, db changes does not get rolled back.
My question is , what is the relation between JTA configuration and DB Connection pool?
Is there any specific configuration in weblogic fot JTA?
How to configure the JTA log in weblogic 10?

Answer 1

For guaranteed transaction atomicity in general, if your application updates multiple transactional resources, an XA-enabled version of the JDBC driver is required to participate in such a global 2PC transaction. If you are absolutely sure that the datasource in question is the only resource accessed in the transaction, then you can mark this datasource as 1PC in the WLS console. Even, if you application enlists multiple resources in a transaction, using the [LLR optimization|http://download.oracle.com/docs/cd/E12840_01/wls/docs103/jta/llr.html] you are still able to use exactly one non-XA resource that must be a LLR datasourse without losing the atomicty guarantee. In order to use LLR, you have to make sure that you don't cache a the LLR datasource connection beyond transaction boundaries, i.e., you need to obtain a new connection from the LLR datasource for every transaction. See http://download.oracle.com/docs/cd/E12840_01/wls/docs103/jdbc_admin/jdbc_datasources.html for more details.
Edited by: Gera Shegalov on Mar 17, 2009 4:44 PM