Summary
This article resolves high CPU consumption of the Deep Security Manager.exe process on Deep Security Manager (DSM) machine.
Details
The large amount of resources consumed might be due to debug logging accidentally enabled or after an upgrade.
To disable debug:
- Stop the DSM service.
- Open the logging.properties file under ..\Program Files\Trend Micro\Deep Security Manager\jre\lib\.
- Comment out or place "#" sign in front of all lines after this line: "For example, set the com.xyz.foo logger to only log SEVERE messages".
- Save the changes and close the file.
- Start the DSM service.
Another option is to simply replace the existing logging.properties file in your machine with this logging properties file that has debug logging disabled.
