How to troubleshoot JVM Memory Error?
- Stop the ManageEngine EventLog Analyzer service.
- Navigate to <EventLog Analyzer home>/server/conf.
- Open the file wrapper.conf.
- Search for wrapper.java.maxmemory.
- Change the default value (1024) to wrapper.java.maxmemory=4096. (The value should not exceed 1/3rd of the overall server memory)
- Save the file and start the ManageEngine EventLog Analyzer service and observe the behavior.
New to ADSelfService Plus?
Related Articles
Error: Low memory detected on Log360's Elasticsearch
Issue description When using build version 12411 and below, you may get this in-product critical notification: Low memory detected on Log360's elasticsearch, increase the memory to at least X GB. This article explains the error message and what ...
Error 500 when loading the GUI
Open the <dir>:\ManageEngine\elasticsearch\ES\logs\wrapper.log file and check the status of Elasticsearch (ES). The log traces below are for reference. INFO | jvm 1 | 2021/06/25 16:08:51 | [2021-06-25T16:08:51,108][INFO][o.e.n.Node][int_Server-Name] ...
Error: "The given servers are not operational" appears when adding domains or domain controllers in Domains & Accounts
Issue description While adding a domain or domain controller (DC) in EventLog Analyzer's Domains and Accounts section and updating the setting, an error popup will display "The given servers are not operational," even if the domain status is active. ...
Error: Windows device status: Access denied
Issue Description Windows device status displays Access Denied post adding the device or while attempting to collect logs. The Access denied error indicates an issue with permissions or security settings preventing access to WMI (Windows Management ...
Error: Time delay in exporting reports from EventLog Analyzer
Issue description Users might experience significant delays when exporting large volumes of report data from EventLog Analyzer, particularly during manual or bulk exports via the web interface. This article offers resolutions for this experience. ...