Hi there! I have the following problem:
I am using Jboss 2.4.6 with CMP (jaws) and Container Managed Transaction. I have a Stateful Session bean with a bussiness method, that utilizes entity beans. The transaction type of that bussiness method is set to "required". When there are many entity beans to be accessed, jboss crashes with the follwing error message: [16:22:34,047,AttributeDetailBean] TRANSACTION ROLLBACK EXCEPTION: javax.transaction.TransactionRolledbackException: removing bean lock and it has tx set!; nested exception is: java.lang.IllegalStateException: removing bean lock and it has tx set! java.lang.IllegalStateException: removing bean lock and it has tx set! at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.removeRef(QueuedPessimisticEJBLock.java:468) at org.jboss.ejb.BeanLockManager.removeLockRef(BeanLockManager.java:78) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:142) .... My guess is, that some of the entity beans are beeing passivated during the transaction, because the problem gets worse if you set the "max-capacity"-parameter in standardjboss.xml to a smaller value. Of course setting the value to a higher number helps in the first place, but isn't a solution to the problem. Any thoughts on that? What is the desired way to use transactions for a bussiness method that itself calls many different methods on a lot of other beans? What happens to a container managed transaction if one of the beans that it utilized is passivated? Any help would be appreciated. Thanks Michael ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
