I am calling dispatcher.runAsync("computeEOQRequirements", context); from
another service to start the job up asynchronously. I have code in
computeEOQRequirements that writes to stdout whenever it first starts. It
seems that it takes like 4 seconds on a fairly skookum machine for it to
begin. The same service runs like instantly when called from the Run
Service button of the Web Tools interface.
The intent is to start the job now, but have it run in it's own thread so
the UI can be interactive for what might be an hour long computation.
Is there any way to control this startup time?
Is there any way to control the thread priority of the job?
Skip
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.519 / Virus Database: 269.21.7/1327 - Release Date: 3/12/2008
1:27 PM
