Transaction marked rolled back

Question

Hi
I'm have a FacadeBean F1 which uses Required transaction attribute which calls another Session Bean S1 which has default transaction attribute(Supports).This uses customized UserTransaction.
In bean S1 this is the sequence of steps
Method{
insert into db
try{
userTransactionBegin.
do some process
userTransaction commit.
}catch{
userTransaction rollback
}finally{
update
Now when a exception is thrown in the process section,The user transaction is rolled back but i get the following exception in the finally block when trying to update some table in DB.
Transaction BEA1-0EB167DB585FC3E8BBFA not active anymore. tx status = Marked rollback.
I believe this happens as the rollback in userTransaction would also cause the transaction to get inactivated and the request to get the fresh DB connection is thrown back with this exception.
Can someone please suggest me what i should do to resolve this issue.
Rgds
Ramraj

Answer 1

Ramraj Chauhan wrote:
Hi
I'm have a FacadeBean F1 which uses Required transaction attribute which calls another Session Bean S1 which has default transaction attribute(Supports).This uses customized UserTransaction.
In bean S1 this is the sequence of steps
Method{
insert into db
try{
userTransactionBegin.
do some process
userTransaction commit.
}catch{
userTransaction rollback
}finally{
update
Now when a exception is thrown in the process section,The user transaction is rolled back but i get the following exception in the finally block when trying to update some table in DB.
Transaction BEA1-0EB167DB585FC3E8BBFA not active anymore. tx status = Marked rollback.
I believe this happens as the rollback in userTransaction would also cause the transaction to get inactivated and the request to get the fresh DB connection is thrown back with this exception.
Can someone please suggest me what i should do to resolve this issue.
Rgds
RamrajHi. You are doing your own tx in the S1 bean, so that beand should be described as
a no-TX (doesn't support tx) bean. That way WLS won't try to involve it in any
calling transaction or control what you do, which is totally independent. You
can't have 'nested' transactions.
Joe