- Hitachi Device Manager (HiCommand Server) may sometimes run out of memory and cause the Sentry’s solutions to fail. This article explains the procedure to follow when this situation occurs.
- CIM_ERR_FAILED, HiCommand Server, Hitachi, Hitachi Device Manager, WBEMException
Hitachi Device Manager Running out of Memory
KB1155 - Aug 21, 2014
Hitachi Device Manager (HiCommand Server) may sometimes run out of memory and cause the Sentry’s monitoring solutions to fail with the following error:
WBEMException: CIM_ERR_FAILED (java.lang.OutOfMemoryError: Java heap space)
This issue occurs when monitoring large Hitachi environments for which a large amount of data needs to be handled. It can easily be solved by increasing the memory heap size of the Hitachi Device Manager.
To increase the memory heap size of the Hitachi Device Manager:
- Open the server.properties file in a text editor. This file is stored in:
- <INSTALLATIONDIRECTORY>\HiCommand\DeviceManager\HiCommandServer\config\server.properties (Windows)
- <INSTALLATIONDIRECTORY>/HDVM/HBaseAgent/agent/config/server.properties (Linux)
- Search for the server.agent.maxMemorySize property. If not present, add it to the file.
- Specify the maximum memory size in megabytes.
Example: server.agent.maxMemorySize=2048, if you want to set the maximum memory size to 2GB.
- Save your file.
- Restart the Hitachi Device Manager service.
The performance of Hitachi Device Manager should now be significantly improved.
- HDS SMI-S Provider: Enabling SMI-S on Device Manager
- HDS SMI-S Provider: Getting Performance Metrics
- Installing the Hitachi Device Manager Agent on Linux
- Leveraging the HSNM2 CLI to Monitor Hitachi (HDS) AMS, HUS Systems
- Monitoring Hitachi Disk Arrays
- Monitoring Hitachi HNAS Storage Devices with Monitoring Studio
- Troubleshooting Issues Related to the Hitachi G-Series and HUS-VM Embedded SMI-S Providers