Hi
>
> Yep, sounds like deadlock to me. Look for cases
> where a client calls a method
> on bean A which calls a method on bean B which calls
> another method on bean A.
> Example from a car registration application:
>
This is a good thought, however, clients are not
allowed to make concurrent calls to beans. If an
instance of 'A' calls an instance of 'B' and 'B' in
turns attempts a call to 'A' you will get a
java.rmi.RemoteException on 'B'. This is mandated by
EJB 1.1 and verified in JCTS...
Hope this helps.
peter
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
