Dead main thread worker

[HansalShah007]

When I run the MOVES scenario using the command ant run -Drunspec="PathToRunSpec\RunSpec.mrs", the documentation says that by default run will also start one worker to process bundles for the MOVES run as long as no other workers are detected. This happens and the initial few (3-4) bundles are processed by a worker, however, after that none of the generated bundles are picked up and processed by any worker. The main thread goes into an endless waiting after all the bundles are generated. Why does this happen? Is it always required to have atleast one worker running on the side using the command ant 1worker -Dnoshutdown=1 or can I just set the -Dnoshutdown=1 flag in the run command, like this?

ant run -Drunspec="PathToRunSpec\RunSpec.mrs" -Dnoshutdown=1

[danielbizercox]

It sounds like the worker thread that is automatically started by MOVES Main in your configuration is in "auto shutdown mode", and quits before MOVES Main finishes generating bundles.

Unfortunately, the run target doesn't look for the -Dnoshutdown=1 argument, so that won't work.

The easiest solution is to start at least one MOVES worker using ant 1worker -Dnoshutdown=1 before calling ant run.