Yes,

When I remove my fix, I see the same error.

The fix is in 2.4, 3.0 and 3.2

You can get the latest versions from CVS,
but you might want to hang fire on 3.0
until a readahead fix has been applied (sometime today?).

Regards,
Adrian

>From: "Chris Pinfold" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>CC: "Terry Hawkins" <[EMAIL PROTECTED]>,"Alan Yost" 
><[EMAIL PROTECTED]>
>Subject: RE: [JBoss-user] Re: "removing bean lock and it has tx set" - 
>question
>Date: Mon, 14 Oct 2002 10:37:55 +1000
>
>We are getting a similar error (see below) from a Stateless Session bean 
>using JBoss 3.0.2.
>We are also using the "Required" transaction attribute.  The error occurs 
>after the following sequence of events:
>1) create some data using entity beans, via a session facade
>2) Shutdown JBoss
>3) Restart JBoss
>4) Remove the data using entity beans, via a session facade
>
>Are we possibly doing something wrong or is this related to the same bug?
>
>Regards
>Chris
>
>This is the error message:
>
>2002-10-10 14:37:50,699 ERROR 
>[com.yambay.mdrover.erp.proxy.session.ERPTestManagerBean] Failed due to 
>remote exception removing bean lock and it has tx set!; CausedByException 
>is:
>       removing bean lock and it has tx set!; CausedByException is:
>       removing bean lock and it has tx set!; CausedByException is:
>       removing bean lock and it has tx set!; nested exception is:
>       javax.ejb.TransactionRolledbackLocalException: removing bean lock and it 
>has tx set!; CausedByException is:
>       removing bean lock and it has tx set!; CausedByException is:
>       removing bean lock and it has tx set!; CausedByException is:
>       removing bean lock and it has tx set!
>javax.transaction.TransactionRolledbackException: removing bean lock and it 
>has tx set!; CausedByException is:
>       removing bean lock and it has tx set!; CausedByException is:
>       removing bean lock and it has tx set!; CausedByException is:
>       removing bean lock and it has tx set!; nested exception is:
>       javax.ejb.TransactionRolledbackLocalException: removing bean lock and it 
>has tx set!; CausedByException is:
>       removing bean lock and it has tx set!; CausedByException is:
>       removing bean lock and it has tx set!; CausedByException is:
>       removing bean lock and it has tx set!
>       at 
>org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:230)
>       at 
>org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:178)
>       at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60)
>       at 
>org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130)
>       at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203)
>       at 
>org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:313)
>       at org.jboss.ejb.Container.invoke(Container.java:720)
>       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
>       at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:98)
>       at 
>org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:102)
>       at 
>org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:73)
>       at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76)
>       at 
>org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:111)
>       at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
>       at $Proxy61.removeJob(Unknown Source)
>       at 
>com.yambay.mdrover.erp.proxy.session.ERPTestManagerBean.clearCache(ERPTestManagerBean.java:661)
>       at com.yambay.mdrover.erp.proxy.session.ERPTestManagerBean.runTestCase
>
>...
>
>
>
>
>
>-----Original Message-----
>From: Adrian Brock [mailto:[EMAIL PROTECTED]]
>Sent: Friday, 11 October 2002 7:40 PM
>To: [EMAIL PROTECTED]
>Subject: Re: [JBoss-user] Re: "removing bean lock and it has tx set" -
>question
>
>
>Hi Michael,
>
>I've applied the fix to the 2.4 branch.
>
>Regards,
>Adrian
>
> >From: Michael Rudorfer <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: [EMAIL PROTECTED]
> >Subject: [JBoss-user] Re: "removing bean lock and it has tx set" - 
>question
> >Date: Fri, 11 Oct 2002 10:47:28 +0200
> >
> >Did I get you right, Bill?
> >
> >You think that this is a bug in Jboss, not a problem with
> >me, using transactions in a wrong way?
> >
> >Michael
> >
> >Bill Burke wrote:
> >
> > > Can you log a bug on this, copy this email, and assign to me?
> > >
> > > patriot1burke
> > >
> > > Thanks,
> > >
> > > Bill
> > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Michael
> > > > Rudorfer
> > > > Sent: Thursday, October 10, 2002 11:38 AM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: [JBoss-user] "removing bean lock and it has tx set" -
> >question
> > > >
> > > >
> > > > 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(Queu
> > > > edPessimisticEJBLock.java:468)
> > > >
> > > >  at
> >org.jboss.ejb.BeanLockManager.removeLockRef(BeanLockManager.java:78)
> > > >
> > > >  at
> > > > org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInter
> > > > ceptor.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
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> >
> >--
> >Dipl.-Inform. Univ.
> >Michael Rudorfer
> >Senior Software Engineer
> >
> >Wearix Software GmbH
> >Unterhachinger Straße 75
> >81737 München
> >
> >Tel.: +49-89-54 88 28-915
> >Fax : +49-89-54 88 28-88
> >
> >www.wearix.com
> >
> >
> >
> >
> >
> >
> >-------------------------------------------------------
> >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
>
>
>_________________________________________________________________
>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>
>
>
>-------------------------------------------------------
>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
>
>
>-------------------------------------------------------
>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


_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com



-------------------------------------------------------
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

Reply via email to