JBoss 2.4 STSB locking - spec violation?

[eprst]

Hi,
We're still using JBoss 2.4.4 and it looks like it uses the same lock for preventing concurrent access to stateful beans and during transaction commits. This means that if some stateful bean B was enlisted in transaction T and B gets called again (may be even without any tx context!) when T is being committed we immediately get an exception.

I was unable to find any place in the spec that describes such behavior (e.g. see 7.5.6 in ejb-2_0-fr2), am I missing something?

PS: we're going to migrate to JBoss 3.x and it would be nice to hear that this issue was fixed :)

Thanks.

[adrian.brock]

Section 7.6.4 bullet point 2

"If a session bean instance is participating in a transaction, it is an error for a client to invoke a
method on the session object such that the transaction attribute in the deployment descriptor
would cause the container to execute the method in a different transaction context or in an
unspecified transaction context. In such a case, the container throws the java.rmi.RemoteException
to the client if the client is a remote client, or the javax.ejb.EJBException
if the client is a local client."

Or have I misunderstood the question?

Regards,
Adrian

[eprst]

Yes, thank you, this section answers my question..