ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SV: Test is using up memory and not even letting it go after test is complete

book

Article ID: 143590

calendar_today

Updated On:

Products

CA Cloud Test Mobile CA Application Test

Issue/Introduction

We have a user who is running a test with a custom logging .jar.  We have run the test with Simulator Heap Sizes of 256mb min - 20gb max.  Then, we increased to 4gb min - 40gb max and it still consumed 75% of heap memory and would not let it go. The final test was when we set the heap to 150gb min - 200gb max. It actually consumed 50% of the memory of that and did not let it go at the conclusion of the test. When we do not use the custom logging .jar, we do not see the consumption issue...everything works fine.  I have attached the tmp folder logs from both the reg coordinator server and the simulator. I see in the coordinator.log a lot of the messages below. You can see them all in the logs. I have also attached the custom logging .jar. 


2019-12-04 21:58:36,552Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.testing.TestAuditor - Audit event buffer is at capacity (256). Consider upping lisa.TestAuditor.buffer.size or figuring out why you are getting so many audit events

2019-12-04 21:58:36,552Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.testing.TestAuditor - Audit buffer contains these events/counts: {Cycle started=256}

2019-12-04 21:58:36,554Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.utils.TestResultsEventListener - (testEvent) Exceeded maximum cycle history events: PF_retrieveAutoPrefillByReportIdnamematching

2019-12-04 21:58:36,554Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.utils.TestResultsEventListener - (testEvent) Exceeded maximum cycle history events: PF_retrieveAutoPrefillByReportIdnamematching

2019-12-04 21:58:36,554Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.testing.TestAuditor - Audit event buffer is at capacity (256). Consider upping lisa.TestAuditor.buffer.size or figuring out why you are getting so many audit events

2019-12-04 21:58:36,554Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.testing.TestAuditor - Audit buffer contains these events/counts: {Cycle started=256}

2019-12-04 21:58:36,554Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.testing.TestAuditor - Audit event buffer is at capacity (256). Consider upping lisa.TestAuditor.buffer.size or figuring out why you are getting so many audit events

2019-12-04 21:58:36,554Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.testing.TestAuditor - Audit buffer contains these events/counts: {Cycle started=256}

2019-12-04 21:58:36,554Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.testing.TestAuditor - Audit event buffer is at capacity (256). Consider upping lisa.TestAuditor.buffer.size or figuring out why you are getting so many audit events

2019-12-04 21:58:36,554Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.testing.TestAuditor - Audit buffer contains these events/counts: {Cycle started=256}

2019-12-04 21:58:36,554Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.testing.TestAuditor - Audit event buffer is at capacity (256). Consider upping lisa.TestAuditor.buffer.size or figuring out why you are getting so many audit events

2019-12-04 21:58:36,554Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.testing.TestAuditor - Audit buffer contains these events/counts: {Cycle started=256}

2019-12-04 21:58:36,555Z (15:58) [ServerRequestResponder 83] INFO  com.itko.lisa.testing.TestAuditor - Audit event buffer is at capacity (256). Consider upping lisa.TestAuditor.buffer.size or figuring out why you are getting so many audit events

Cause

There was a potential memory leak identified and a patch has been prepared to address the same.

Environment

Release : 10.5

Component : CA Application Test

Resolution

Patch was provided that resolved the issue -  patch_DE441522_10.5.0_LTD.jar 

Steps to Apply The Patch:

1. Download the patch ( please open a ticket and reference  DE441522)

2. Stop all DevTest Services

3. Place the patch file in folder LISA_HOME\lib\patches. If the 'patches'' folder doesn't exist, please create the same

4. Start DevTest services that were stopped in step 2

Run your tests  and see results.