Ingo Schuster wrote:
>
> Hello,
>
> What happens to a running thread in the EJB container when the client that
> initiated the call gets terminated?
If the enterprise bean method that get called has transaction enabled
and make call from time to time to other beans, you will get a
TransactionRolledBackException when the transaction will timeout (every
transaction will timeout at one moment or another if it take forever to
execute). I suspect that if the thread run wild, the AppServer will
terminate it - I don't know how because the method required to do that
are deprecated.
But you are defying the EJB spec by trying to achieve your goal.
If you really need something to run forever, you should not do it with
EJB. Use your App Server thread capability (if it has one, like
WebLogic) or JMS or develp your own thread services that could be
accessed with RMI.
--
Emmanuel Pirsch
Sun Certified Java Programmer
Unite for Java! - http://www.javalobby.org/
---
"The intuitive mind is a sacred gift and the rational mind is a faithful
servant. We have created a society that honors the servant and has
forgotten the gift."
- Albert Einstein.
===========================================================================
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".
