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".
