Or just switch QueuedPessimisticEJBLock to MethodOnlyEJBLock. It may work,
may not. I haven't thought through all the possibilities. Try it at your
own risk.
Bill
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Ferguson, Doug
> Sent: Wednesday, September 19, 2001 9:55 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
>
>
> Does this mean that if you leave all the interceptor then there
> is no transactional locking on the bean?
>
> This is an easy way to get ReadOnly before it gets implemented..
>
> d.
>
> -----Original Message-----
> From: Bill Burke [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 19, 2001 10:53 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
>
>
> Todd,
>
> I cannot reproduce this problem. You're going to have to give me a test
> case before I believe you. Also, do you use standardjboss.xml to create
> your Entity Bean configuration? Or do you make your own. If you use
> standardjboss.xml, please attach this to your next reply.
>
> PLEASE NOTE!
>
> There has been an extra interceptor added to the interceptor
> chain in 2.4.1.
> Please look in the distributed standardjboss.xml that comes with 2.4.1.
> EntityLockInterceptor should be in the interceptor chain, and also a new
> field <locking-policy> should be set to QueuedPessmisticEJBLock.
>
> i.e.
>
> <container-configuration>
> <container-name>Standard CMP
> EntityBean</container-name>
> <call-logging>false</call-logging>
>
> <container-invoker>org.jboss.ejb.plugins.jrmp.server.JRMPContainer
> Invoker</c
> ontainer-invoker>
> <container-interceptors>
>
> <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
>
> <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
>
> <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
> <interceptor
> metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</in
terceptor>
>
> <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor>
>
> <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
>
> <interceptor>org.jboss.ejb.plugins.EntitySynchronizationIntercepto
> r</interce
> ptor>
> </container-interceptors>
>
> <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
>
> <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
>
> <persistence-manager>org.jboss.ejb.plugins.jaws.JAWSPersistenceMan
> ager</pers
> istence-manager>
>
> <transaction-manager>org.jboss.tm.TxManager</transaction-manager>
>
> <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLoc
> k</locking
> -policy>
> <container-invoker-conf>
> <RMIObjectPort>4444</RMIObjectPort>
> <Optimized>True</Optimized>
> </container-invoker-conf>
> <container-cache-conf>
>
> <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolic
> y</cache-p
> olicy>
> <cache-policy-conf>
> <min-capacity>50</min-capacity>
> <max-capacity>1000</max-capacity>
>
> <overager-period>300</overager-period>
> <max-bean-age>600</max-bean-age>
> <resizer-period>400</resizer-period>
>
> <max-cache-miss-period>60</max-cache-miss-period>
>
> <min-cache-miss-period>1</min-cache-miss-period>
>
> <cache-load-factor>0.75</cache-load-factor>
> </cache-policy-conf>
> </container-cache-conf>
> <container-pool-conf>
> <MaximumSize>100</MaximumSize>
> <MinimumSize>10</MinimumSize>
> </container-pool-conf>
> <commit-option>A</commit-option>
> </container-configuration>
>
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Todd
> > Huss
> > Sent: Tuesday, September 18, 2001 8:16 PM
> > To: [EMAIL PROTECTED]
> > Subject: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
> >
> >
> > I just upgraded from JBoss 2.4.0 to JBoss 2.4.1 and noticed some of the
> > locking code has changed. I have an entity bean with all methods having
> > the transaction attribute set to "RequiresNew" and works great
> under JBoss
> > 2.4.0. As soon as I upgraded to 2.4.1 though, I started getting race
> > condition errors in this particular entity bean.
> >
> > In 2.4.1, RequiresNew methods are currently allowing simultaneous method
> > calls on the same bean where one of the calls should block
> until the other
> > one completes (and it does in 2.4.0). I was able to reproduce the race
> > condition and then downgrade to 2.4.0 and everything worked great again
> > with one of the method calls blocking as expected, then
> upgrading back to
> > 2.4.1 one more time showed the race condition again.
> >
> > Lastly, is there a bugzilla or something similar for JBoss where I can
> > submit bug reports, or is this the best place to do it?
> >
> > Thanks,
> > Todd
> >
> >
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
