|
Home > Archive > WebSphere Application Server > March 2006 > Naming and Prioritising Asynch Beans/CommonJ Work Threads?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Naming and Prioritising Asynch Beans/CommonJ Work Threads?
|
|
| EoinWoods 2006-02-20, 5:56 pm |
| When using unmanaged threads, you can both name a thread, via Thread.setName(), and set its priority, via Thread.setPriority().
Can you achieve either of these things for managed threads inside WAS 6? (Started either via the CommonJ or Asynch Beans WorkManager). I can't see any obvious way to achieve this from the JavaDocs.
Thanks for any thoughts.
Eoin.
--
Eoin Woods, UBS Investment Bank, London
| |
| Chris D Johnson 2006-03-13, 5:56 pm |
| > When using unmanaged threads, you can both name a thread, via
> Thread.setName(), and set its priority, via Thread.setPriority().
You can set the thread priority at the WorkManager level (in the WorkManager
configuration), but it applies to all threads. The name of the thread and
the priority or otherwise not accessible to applications.
-- Chris
|
|
|
|
|