Thank you for timely reply.
Yes, I'm running cache & EJB in same JVM.
This is the case, I need to look for alternative design.
Thank you very much
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239176#4239176
Reply to the post :
http://www.jboss.org/index.
On the other post I saw you're using DummyTransactionManagerLookup. You're
running in the application server so use GenericTransactionManagerLookup.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238985#4238985
Reply to the post :
http://www.jboss.org/index.
Are you running both EJB's in the same JVM? That would explain it, as TX
rollback won't affect the changes you've done to TestEntity, only the
operations you've done on cache. That is the changes TestEntity.update does on
the object won't be affected by the TransactionManager.rollback call. Fol
I have tried with Isolation level READ_COMMITTED also.
I have replaced array in my TestEntity object, but still the same problem
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238850#4238850
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=p
