Make sure you check all threads as well as the process in the NetConfig.
Also, it is possible to turn up EO Config at the thread or process level from the NetMonitor. The setting gets set back to the NetConfig setting when the thread/process is stopped and started or when it is reset manually in the NetMonitor.
So if you find it has been set at the NetConfig somewhere, you can change the NetConfig and then just change the same object in the NetMonitor eliminating the need to sycle the object and affect message flow.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
The only way you can tell if it was turned on in the NetMonitor is to check the log (the NetMonitor ‘Command and Engie Output’ view will also show) if the log has not been cycled.
It is my guess this was turned on in the NetMonitor.
If you want to take the time, you can tell from the Process log if the noise is turned up at the process or thread level and even what thread.
However, if you just want it to stop, then turn the EO Congig down at the process level in the NetMonitor.
Then it won’t start again (assuming the NetConfig doesn’t have it set) unless someone does it from the NetMonitor.
There is nothing wrong with using the NetMonitor to turn up the EO COng – one just needs to remember to turn it back down or off once the need for the log information has passed.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
Author
Replies
Viewing 2 reply threads
The forum ‘Cloverleaf’ is closed to new topics and replies.