...
- WindRiver Lab, APPC Project
- Due to a defect that is blocking sending and receiving DMaaP messages in the Beijing code the Amsterdam release code was used during the APPC 72 Hour Stability test.
- The Final Completion notification for each transaction is not returned to create a final completion result for this test. The final completion will be integrated and tested with the Beijing code once defect APPC-658 is corrected.
Test Execution:
- The test was kicked off via cron set to run for 72 hours.
- The fully automated "closed-lopp" type test wherein Athe test is kicked off and waits for the transaction completion to be received before sending another request will be enabled in the testing once APPC-658 is resolved.
- Command to execute the test: ./jmeter.sh -n -t ../APPC-LCM-Action-V1.jmx -l ../APPC-LCM-Action-V1.jtl' > /dev/null 2>&1 &
...
- The test was executed for 72 hours with the APPC environment remaining up and successfully processing transactions during that time.
- The results from the test are logged in the APPC-LCM-Action-V1.jtl file on the Test Client Server
- The APPC application logs logged the results on the APPC side:
- karaf.log
- Service Logic logs (DG logs)
- Notes/Observations:
- The performance monitor collecting statistics for the APPC VM CPU, Memory etc... crashed during the test. A cronjob will be created going forward to check for the existance of the client running on APPC and will restart the process if it is down. This is not APPC code but is part of the JMeter Performance monitoring plugin.
- Sample Stop Request:
| Code Block |
|---|
From the JTL Log: 1521776330123,18013,Stop Transaction Controller,,"Number of samples in transaction : 4, number of failing samples : 3",Stability-Test-VM2 LCM Group 2-1,,false,,2231,2180,1,3,18013,90014,3 1521776438150,3,Submit request via DMaaP,200,OK,Stability-Test-VM2 LCM Group 2-1,text,true,,332,1223,1,3,3,0,0 |
...