Why does Java.exe use a high amount of RAM on servers?
Possible causes:
The high RAM utilization by the Java.exe used in ADManager Plus could be due to various factors.
Multiple parallel scheduled reports, automations, exports, or synchronizations may be occurring simultaneously.
More number of attributes might be selected in reports.
The operational DC or the nearest DC might not be configured as the primary DC.
The environment might have a large number of objects and configurations, such as schedules, automations, and exports, which can use a significant amount of memory.
Solution:
Avoid running reports or automation schedules simultaneously and ensure sufficient time intervals between them.
Make sure the nearest DC is configured as Primary DC or Enable DC Sort Intelligence in Domain/Tenant Settings.
To enable DC sort intelligence,
Navigate to Domain/Tenant Settings > Domain Configuration.
Click Edit Domain Details.
Check DC Sort Intelligence.
Check for any possible scenarios or reasons in your environment and take appropriate measures, such as reducing the number of parallel schedules.
Refer to this page to obtain the system requirements for environments with a large number of objects and configurations.
New to ADSelfService Plus?
Related Articles
Error: pgsql\bin\pg_ctl.exe does not exist or is being used by another program
Issue description When starting ADManager Plus, the application fails to launch and displays an error indicating that pg_ctl.exe is missing or in use. This prevents the internal PostgreSQL database from starting, resulting in a complete startup ...Why are deleted DFS namespaces still appearing on file servers?
Issue description After deleting a DFS namespace through the DFS Management snap-in, it may continue to appear on DFS file servers due to inconsistencies in DFS metadata. This can cause confusion, disrupt DFS operations, and make it difficult to ...Pre-requisites for configuring High Availability
Pre-requisites for configuring High Availability in ADManager Plus: 1. Ensure that both the instances of ADManager Plus: a. Are running as a service. b. Have the same build architecture (32-bit or 64-bit). c. Are updated to the latest build. d. Have ...Remove High Availability setup in ADManager Plus
How to break HA setup: Please stop the ADManager Plus in services.msc in the Primary and Secondary servers. Please download the files from the attachment at the bottom of this article. Place the RemoveHASettings.bat file in the bin folder of the ...Incase of high CPU / memory usage, please help us with the below information,
1. Build number: 2. DB with version: 3. RAM size: 4. Current memory consumption: 5. Available disk space: 6. No of domains: 7. No of users/computers: 8. No of groups/OU: 9. No of automations configured: 10. No of Help Desk Technicians : 11. No of ...