Hi folks,
I was wondering about two things which I didn't find any explicit discussions
about in the archives, regarding thread priorities in beans. I think the
question is as applicable to the 1.1 spec as the 2.0 draft...
1) If I have a startup class (same JVM as app server, PowerTier 6.53 in this
case) with a low priority and call beans from it, will the beans execute
with the same thread priority of the startup class? The spec
(18.1.2/23.1.2) only mentions that a bean is not allowed to _change_
thread priorities. But what's the behaviour if the thread's priority was
set in a calling class, outside the bean? Is there any risk of messing up
the app server's internal threading control by doing this? Or does the
priority not carry into the bean at all?
2) This might be a silly question, but assuming the thread priority carries
into the bean, is it possible to do the same thing over RMI/IIOP? E.g.,
a remote client calling a bean in a low/high priority thread, and have
the bean instance on the server execute with the same priority?
Note that I'm not talking about manipulating threads _in_ a bean, only how the
priorities carry from calls made into beans from non-bean classes.
Anyone who could offer more insight?
Cheers,
Jonas
===========================================================================
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".
