In VPLUI.webSocketMonitor, the retrieve and cancel actions use the global process ID from VPLUtil.getProcessId(). This may (in rare cases) lead to sending a retrieve or cancel action on the wrong process, since the global ID can be changed by subsequent processes (if for example the close signal comes a little late and the next process is launched early).
This PR fixes it. We simply use coninfo.processid which is a parameter of the websocket monitor, keeping a consistent process ID for a given monitor.
In
VPLUI.webSocketMonitor
, the retrieve and cancel actions use the global process ID fromVPLUtil.getProcessId()
. This may (in rare cases) lead to sending a retrieve or cancel action on the wrong process, since the global ID can be changed by subsequent processes (if for example the close signal comes a little late and the next process is launched early).This PR fixes it. We simply use
coninfo.processid
which is a parameter of the websocket monitor, keeping a consistent process ID for a given monitor.