Ganesh,
Thanks for your help.
My problem is I don't want the first session bean to hang when the second
session bean goes to infinite loop. I found that the Weblogic use the
session bean descriptor timeout as transaction timeout. But how about if
the bean is not running in transaction context? Besides, it seems not all
the EJS vendor use that descriptor timeout as transaction timeout. Do you
think in specification 1.0 the descriptor timeout value meant to be the
transaction timeout value not idle timeout value?
Best Regards
Jie Hu
[EMAIL PROTECTED]
"Venkataraman, Ganesh K" <[EMAIL PROTECTED]> on 03/22/2000
05:55:21 PM
Please respond to "Venkataraman, Ganesh K"
<[EMAIL PROTECTED]>
To: Jie Hu/Toronto/IBM@IBMCA
cc:
Subject: FW: Is it possible to have client timeout in EJB?
I once had some problem with session timing out and I fixed it by
incrementing the session timeout seconds in the deployment descriptor.
I think it just depends on how you deploy your beans. Why do you
want your first session bean to time out if the second session bean takes a
longer time. Can you give me an example of what you're trying to achieve.
If you specify the timeout for the first session bean to a time less
than the second session then when the second session bean takes more time
the first will automatically timeout. I am not sure If this is of any help,
but if given a scenario I could probably help.
Regards
Ganesh
-----Original Message-----
From: Jie Hu [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 21, 2000 9:27 AM
To: [EMAIL PROTECTED]
Subject: Is it possible to have client timeout in EJB?
Hi all,
Does anybody know how EJB container handles timeout? I have posted this
question before and haven't got any answer yet. I re-post it and hope this
time can generate some response. I am thinking to handle timeout situation
in EJB. Let say an EJB client (a sesssion bean) calls another session
bean, if the second session bean take to long to return, the first session
bean want to timeout. My understanding of EJB seems suggest this is not
possible. Because of the first EJB client can not spawn any thread to
implement a timer. Even it can, then it may be dangerous to early terminate
the call due to there may be transactions involved. I noticed there is a
timout attribute in Session bean deployment descriptor. The spec does not
have detailed description on the attribute. I found WebLogic use the value
as transaction timeout. It so, if my session bean involved with
transaction, I may be I can just rely on setting this value to have
transaction exception thrown when the timeout occoured. But how about if
there is no transaction involved?
Has anybody have experience with timeout value in WebLogic?
Any help will be very appreciated!
Jie Hu
[EMAIL PROTECTED]
===========================================================================
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".
