...
The APPC 72 Hour Stability Test was kicked off at xx 23:00 GMT on xxxday xxx xxTuesday Nov 6, 2018. The APPC environment remained up and processed requests during the entire test period without crashing.
...
- WindRiver Lab, APPC Project
- APPC Casablanca: 10.12.5.174, 10.12.5.193, 10.12.5.194
- Test Client VM: 10.12.5.171
- A&AI: 10 10.108102.4066.103160
- DMaaP MR: 10.111103.1895.177
Test Execution:
- The test was kicked off via cron set to run for 72 hours.
The fully automated "closed-loop" type test where the 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: /home/ubuntu/testing/apache-jmeter-4.0/bin/jmeter.sh -n -t ./APPC-LCM-Action-V1.jmx -l ./APPC-LCM-Action-V1.jtl > /dev/null 2>&1 &
nohup /home/ubuntu/testing/apache-jmeter-4.0/bin/jmeter.sh -n -t ./forever_APPC-LCM-Action-V1.jmx -l ./APPC-LCM-Action-V1_run72hr_1651GMT_6_11.jtl >/dev/null 2>&1 &
Test Results:
- 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
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.
- karaf.log
Sample Stop Request: from the JTL Log
...