Owners Manual

Linux Issues | Troubleshooting
728 OMNM 6.5.2 User Guide
2 If TOP reveals an excessive and abnormally high memory usage for the application java
process, you may need to restart your application server and evaluate installed/available
memory with regard to your sizing and application usage requirements. Install more server
memory as needed.
II. Genuine memory issues appear if logs contain an error like
java.lang.OutOfMemoryError: GC overhead limit exceeded , and application
server performance is slow, possibly preventing log into web portal. You may also see many other
errors, for example, from performance monitoring:
WARN [com.dorado.broadscope.polling.PollingResultsDAOImpl]
(WorkManager(2)-99:) Low on memory. Discarding this batch.
Solution: These errors indicate memory resources are low or have been depleted.
To address this, first review any potential causes for an increase in memory usage. For example, has
there been a significant increase in performance monitor load, perhaps from reducing polling times
or an increase in targets/attributes? Have there been any other changes?
Assuming sufficient server memory is available, increase heap size. Adjust memory values below
according to your environment and configuration needs:
1 Shut down the application.
2 Open owareapps/installprops/lib/installed.properties file for editing.
3 Modify the oware.server.max.heap.size property
oware.server.max.heap.size=3072m
In this example, a recommended increase would be 25% to 4096m.
4 Increase oware.server.min.heap.size to match (4096m)
5 Save changes to installed.properties .
6 Restart the application.
NOTE:
Heap adjustments work for Windows too.
III. Out of Memory errors like Out of Memory: unable to create new native
thread
in logs for server (application or mediation) may indicate memory resources are sufficient,
but threads are not.
Solution: The operating system may be limiting the number of available threads for use by the
application. Check/modify the
ulimits settings with these steps:
1 Open shell/CLI and type ulimits -a .
Open files and User Processes should not be set to typical defaults (1024). Change these with
the next steps.
2 Open /etc/security/ limits.conf for editing.
3 Add the following lines and save.
<installing user> soft nofile 65536
<installing user> hard nofile 65536
<installing user> soft nproc 65536
<installing user> hard nproc 65536
4 Restart the application processes.