-
Type:
Bug
-
Resolution: Tracked Elsewhere
-
Priority:
Low
-
None
-
Affects Version/s: 7.10.2
-
Component/s: Troubleshooting and Support Tools (ATST)
-
7.1
-
Severity 2 - Major
Summary
Problem 1: Hercules Scan is CPU intensive (taking > 90% CPU resources) and it was triggered automatically when visiting page: "Troubleshooting and support tools".
Problem 2: Hercules thread cannot stopped in certain condition, when you click on "Troubleshooting and support tools" page, Log analyzer/Hercules is automatically triggered, at this point if you click "Cancel" on UI the hercules thread status will change from Running to Timed_Waiting which is expected. Here comes the problem, visit the page "Troubleshooting and support tools" > Log analyzer started > Before it completes, visit the page again "Troubleshooting and support tools" > Noticed the status stucks at 0% > Cancel the operation on UI > Thread is still shown as Running,


Expected Results
Problem 1: Hercules scan should not be taking so much CPU and it shouldn't start scanning automatically when visiting page: "Troubleshooting and support tools".
Problem 2: Hercules scan should not be executed again when visiting the page 2nd time, or better yet do not allow auto-trigger when visiting the page. And also, the thread should be allowed to cancel even though the page is visited multiple times.**
Actual Results
Problem 1: Hercules scan is taking too much CPU > 90% and it auto-triggered when visiting the page.
Problem 2: Hercules thread cannot be stopped when visiting the page multiple times.
- cloned by
-
ATST-910 Loading...