Which version of jboss?
Try the latest and greatest :-)
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 ???
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
3.0.5 contains some other fixes for related bugs.
I got the exact same problem with 3.0.5 and 3.0.6 ?
Is the bug fixed yet ?
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.
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.