Differences

This shows you the differences between two versions of the page.

--- resolution_area:watchdog_resolutions:res-w9402 [2021/06/25 10:09] – external edit 127.0.0.1
+++ resolution_area:watchdog_resolutions:res-w9402 [2021/07/05 20:47] (current) – 10.91.120.28
@@ Line 1: / Line 1: @@
 =====GarbageCollectionOutOfMemoryErrorFound=====
-**Level:** __Critical__
+**Level:** __Critical__ FIXME
-**Purpose:**
+**Purpose:** The monitored application has used all its memory resources, garbage collection is yields little to no return resources. If the application is still running at this stage is unlikely or barely unusable. Actions need to be taken to resolve the problem
-**Scenario:**
+**Scenario:** Reporting Manager has used all its memory, a report has been run which try's to render 100's of thousands of rows in the front end of the Reporting Manager.
-**Resolution:**
+**Resolution:** Restart the Reporting Manager
 **Manual Action Steps:**
+\\
-**Auto Clear:**
+Script Based Restart
+<code>
+cd /var/tomcat/ReportingManager/bin/
+./shutdown.sh
+ps aux | grep -i Reporting
+(Kill process if still running: kill $pid)
+./startup.sh
+</code>
+\\
+Ansible
+<code>
+ansible-playbook -i ../env-configuration/${env}/hosts.ini --diff --vault-id @prompt reportingmanager.yml -e "actions='stop,start'" --limit $appHandler
+</code>
+**Auto Clear:** Yes, but with a 30 minute check back. Warning, this alarm will clear after 30 minutes from the point the log was seen by WD. The application could still not be usable if action was not taken and this time passed

Internal Errigal Collaboration Wiki