Idea ID 1791127
In the VMware adapter we have several VMware related jobs that have the job parameter runInSeparateProcess OOTB on True. We don't recommend using it on false https://docs.microfocus.com/UCMDB/2018.05/cp-docs/docs/eng/doc_lib/Content/VMInfra_R_ESX_tplgy_VIM_jb.htm
When true, this enables the execution of the job in the external java virtual machine.
Note: Do not change this parameter from the default.
If we move this parameter on false then we need to alter the DFP classes to include in DataFlowprobe\conten\lib\vmware the VMware vim25.jar file like in the documentation. In most cases it will fail due to the classpath of the probe.
The jobs which don't use a separate process are: ESX Connection by CIM, ESX Topology by CIM, VMware TCP ports and the vROps jobs. This jobs are not affected by any kind of separate process. They won’t change or won’t be affected.
The rest of the jobs do have this parameter and it's always on True.
By default we should remove this parameter and hardcode it on true so there will be only the option to run these jobs (except the ones mentioned above which don't have this parameter) only in a separate process as time showed that they work better this way and if they fail then the DFP JVM is safe as only the separate process will crash.
The JVMargs should be suggested depending on each job. For example the Vmware Connection by VIM job needs little memory as it will report 10-15CIs for each trigger CI but the vCenter Topology by VIM needs at least 3GB of HEAP memory as it can report well over 100k CIs for each trigger CI. Currently we have no suggestions on the parameter runInRemoteProcess and we use a global value for all the jobs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.