Sripada,
An EJB Container cannot remove/passivate a bean that is in txn. So, if your
bean is locked in a client txn, it is stuck! However, setting a timeout
value for your transaction will alleviate this issue, by timing out the txn
first, thereby, allowing the EJB Container to timeout the entity bean!
Hope this helps.
Jason
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Sripada Srinivas
Sent: Wednesday, March 22, 2000 11:47 PM
To: [EMAIL PROTECTED]
Subject: Time out of Entity beans??
Hi,
I am wondering what happens when I invoke a request on an entity bean,
then the client goes to an indefine lull.
Then the EJBObject at the server may implement passivation, but still it
is holding the primarykey reference of the entity bean instance or
someother machanism for later invocation.
But I want to know if anything called can be applied to Entity beans
also, so that the EJBObject is relieved of its effort to keep track of
the client who has invoked and then went dead.
Regards,
Sripada
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
