Stateful bean with different tx context-urgent

boobalan_kj Nov 8, 2006 2:39 AM

when multible users accessing the application I am getting the following log message...

INFO | jvm 1 | 2006/11/02 13:45:29 | 13:45:29,216 ERROR
[LogInterceptor] TransactionRolledbackLocalException in method: public abstract void javax.ejb.EJBLocalObject.remove() throws javax.ejb.RemoveException,javax.ejb.EJBException, causedBy:
INFO | jvm 1 | 2006/11/02 13:45:29 | javax.ejb.EJBException:
Application Error: tried to enter Stateful bean with different tx context, contextTx: TransactionImpl:XidImpl[FormatId=257,

I am using the REQUIRED transaction attribute and default container configurations(STANDARD for CMP2.x).which uses QueuedPessimisticLock..
I am getting lot of ApplicationDeadLockException..I tried to use Instance Per policy but that is getting more dirty reads.

how do i get rid of this problem?

Thanks in advance
bala.

1. Re: Stateful bean with different tx context-urgent

jokum Dec 5, 2006 3:34 PM (in response to boobalan_kj)

I'm getting the exact same problem.

Anybody has some ideas please?

I figured out it could be a solution to synhronize the SFSB instance using a container interceptor in standardjboss.xml. How can I do this?

Thanks in advance,
Actions