AnsweredAssumed Answered

Boomi maintenance task is trying to clean up a JMX monitoring process

Question asked by scott.romney on Oct 5, 2016

This logging message from logs/2016_10_04.container.*.log is probably not a sign of a serious issue, but I'd like to get a second opinion. It appears that the maintenance task for cleaning up aborted workers is trying to act on the Datadog 

VM on the same host that is providing JMX stats on the Boomi process:

 

Oct 4, 2016 7:42:05 PM UTC WARNING [com.boomi.execution.forker.SunForkedProcessHandler getKnownRunners] Failed processing sun.tools.attach.LinuxAttachProvider@81ab0c6: 9796 org.datadog.jmxfetch.App --check jmx.yaml --check_period 15000 --conf_directory /etc/dd-agent/conf.d --log_level INFO --log_location /var/log/datadog/jmxfetch.log --reporter statsd:localhost:8125 --status_location /opt/datadog-agent/run/jmx_status.yaml collect
com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: target process not responding or HotSpot VM not loaded
at sun.tools.attach.LinuxVirtualMachine.<init>(LinuxVirtualMachine.java:106)
at sun.tools.attach.LinuxAttachProvider.attachVirtualMachine(LinuxAttachProvider.java:78)
at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:250)
at com.boomi.execution.forker.SunForkedProcessHandler.getSystemPropertiesForVM(SunForkedProcessHandler.java:433)
at com.boomi.execution.forker.SunForkedProcessHandler.interrogateVm(SunForkedProcessHandler.java:354)
at com.boomi.execution.forker.SunForkedProcessHandler.getKnownRunners(SunForkedProcessHandler.java:296)
at com.boomi.execution.forker.SunForkedProcessHandler.getExecution(SunForkedProcessHandler.java:263)
at com.boomi.execution.forker.SunForkedProcessHandler.isExecuting(SunForkedProcessHandler.java:148)
at com.boomi.execution.forker.MultiProcessExecutionForker.reapAbortedWorkers(MultiProcessExecutionForker.java:798)
at com.boomi.execution.forker.MultiProcessExecutionForker.runMaintenanceTasks(MultiProcessExecutionForker.java:750)
at com.boomi.container.cloudlet.execution.ClusterExecutionForker.runMaintenanceTasks(ClusterExecutionForker.java:515)
at com.boomi.execution.ExecutionManager.runMaintenanceTasks(ExecutionManager.java:771)
at com.boomi.execution.ExecutionManager.access$100(ExecutionManager.java:54)
at com.boomi.execution.ExecutionManager$2.run(ExecutionManager.java:403)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

 

For anyone who has access to the source, how does the SunForkedProcessHandler get the list of VMs that it interrogates? Can it be changed to ignore the non-Boomi Datadog VM?

Outcomes