>
> HI All,
> I've got a startup class which spawns a low priority
> thread and sleeps &
> wakes up
> every hour. Is this OK behaviour ? I know that one
> *shouldn't* create &
> use threads
> in WL (4.5.1), but does this apply to startup classes ??
Threading restrictions only apply to the EJB container. Startup classes run
outside the EJB container, so the limitation does not apply.
>
> Another option is to have an infinite loop in my startup
> class which
> sleeps for the
> time and then wakes up .... this assumes that WL instantiates
> & runs its
> startup
> classes in a separate thread ... which I don;t think it does ?
>
I would spawn a thread (as you're doing now) so as not to depend on this
behaviour.
- Avi
--
s/\be(\w+)/e-\1/g;
===========================================================================
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".
