Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In Java EE 5, when using timers and the timer service, who handles the timeout invocation?
Can I be sure that the stateless session bean which created the timer wil be the one to handle its timeout (with a @Timeout annoateted method)? or there’s no way of telling which bean (of the same type) will handle it?
Also, Is there any difference on that issue between Java EE 5 and 6?
No, there’s no guarantee. To provide such, an SLSB would have to be “reserved” somehow (doing nothing) to make sure it’s available when the timeout elapses, which would make it, well, stateful. It’s likely that for this very reason, timers cannot be used in stateful beans.