Currently, its possible to set the java heap size the TaskRunner child runs in, but thats all thats configurable about the child process. Hereabouts, we've found it useful being able to specify other options for the child JVM, especially when debugging and monitoring long-lived processes.
Examples of why its useful being able to set options are the child include:
+ Being able to set '-server' option or '-c64'.
+ Passing logging.properties to configure child logging.
+ Enable and capture to file verbose GC logging or start the SUN JVM JMX agent for the child process. Allows connecting with jconsole to watch long-lived children, their heap and thread usage, and when seemingly hung, take thread dumps.