public class PlanWorkerApplication extends AbstractWorkerApplication
Having one new process per plan is overkill in terms of RAM usage. Hence shiva uses one dedicated thread per plan.
application, applicationFolder, clusterName, confDirFolder, ephemeral, executionTime, hasStarted, lastExecutionStart, numExecution, platformReporter, workerId| Constructor and Description |
|---|
PlanWorkerApplication(String workerId,
String clusterName,
Path dataFolder,
Path folder,
org.thales.punch.libraries.shiva.api.Application application) |
| Modifier and Type | Method and Description |
|---|---|
int |
exitValue()
exit value here refers to a thread that dies or not; thus the plan thread itself and not the subprocess executed by plan thread
|
boolean |
isAlive() |
boolean |
start()
Start a worker task, i.e.
|
void |
stop()
Stop a worker task, i.e.
|
getApplication, getClusterName, getFolder, getName, getWorkerId, isEphemeral, isEverRunningTask, isStarted, launchChildApplication, started, taskShouldRunNow, toStringpublic boolean isAlive()
isAlive in class AbstractWorkerApplicationpublic boolean start()
AbstractWorkerApplicationstart in class AbstractWorkerApplicationpublic void stop()
AbstractWorkerApplicationstop in class AbstractWorkerApplicationpublic int exitValue()
exitValue in class AbstractWorkerApplicationCopyright © 2022. All rights reserved.