-
1. Re: removing bean lock and it has tx set!
adrian.brock Jan 22, 2003 7:46 PM (in response to pope)Which version of jboss?
Try the latest and greatest :-)
Regards,
Adrian -
2. Re: removing bean lock and it has tx set!
pope Jan 24, 2003 3:33 AM (in response to pope)jboss 3.0.3
I think i find out the problem. It is something about the
cache size. After enlarging the cache size for CMBeans a never got that error again.
My question remains...what that message for ??? -
3. Re: removing bean lock and it has tx set!
adrian.brock Jan 24, 2003 9:47 AM (in response to pope)That bug was fixed in 3.0.4, it was a race condition
between passivation and invocations.
By increasing the cache size you made passivation
less likely.
3.0.5 contains some other fixes for related bugs.
Regards,
Adrian -
4. Re: removing bean lock and it has tx set!
christian Feb 14, 2003 5:01 PM (in response to pope)I got the exact same problem with 3.0.5 and 3.0.6 ?
Is the bug fixed yet ? -
5. Re: removing bean lock and it has tx set!
adrian.brock Feb 16, 2003 8:07 PM (in response to pope)I did find another cause for this problem
fixed for 3.0.7. This happens when ejbActivate or
setEntityContext throws an Error.
More likely is one of the following problems.
You haven't implemented your primary key correctly
specifically hashCode(), equals(Object) or the
serialization, or you are changing the primary key?
This can cause the lock manager to loose track
of the lock.
Regards,
Adrian -
6. Re: removing bean lock and it has tx set!
powertoaster Mar 11, 2003 2:20 AM (in response to pope)Another way to cause this error is to attempt a remove while the bean in question is in use. Kind of obvious but it happens.