>From what I can tell, when a CMT bean times out (at least in the case of 3.2.6
>and Stateless Session Beans), the transaction is simply marked as
>setRollbackOnly, but no exception is explicitly thrown. This leads to a
>situation where the bean can return data but the data is not consistant wi
I have two EAR files (A and B). Each contains a standard Stateless Session Bean among
other things. Bean a in EAR A makes a standard EJB call to bean b in EAR B.
We have found that hot deploying either of these EARs without the other causes
problems. The following exception is generated:
C
