I'm using the 3.0 beta, and followed the source code for
configuration.setTaskExecution(long ms), it seems to bind the values
at the time I call
officeManager = configuration.buildOfficeManager();
It calls
new ProcessPoolOfficeManager(xxx, including the task timeout)
which creates settings, and does
pooledManagers[i] = new PooledOfficeManager(settings);
Although I don't completely understand the code, it seems the task
timeout value is bound at the time the pool of office managers is
created.
I can do ((ProcessPoolOfficeManager)officeManager), but really need to
get the PooledOfficeManager that is being used to set the timeout
there.
I'm not sure if the correct plumbing is in place in the 3.0 version to
set per-task timeout. (Is the 3.0.4 version the same as the 3.0 beta
version?)