Started hunting down the possible bugs in task generation.
Trying to track down the nil named tasks within the startup of a cpu and during task generation.
Forced some names on the nil tasks that were being generated. Added some more output for instrumenting the bug.
Took out some debug print statements that are not used.
Added more output lines to determine if a task was successfully set up.
There may be a difference in operation of locks between Oracle and
OpenJDK VMs. Erratic startup behavior appears to be fixed by
instantiating all startup tasks without locking. This operation should
be ok.