> On Feb 1, 2016, at 11:52 AM, Chris Pike <[email protected]> wrote: > > When running the load test for A, there doesn't seem to be a profile for > loadtest-ftca. >
Thanks for pointing this out. I sent the wrong command. Here is the corrected: A. Fortress CheckAccess: ``` mvn -Ploadtest-fortress jmeter:jmeter ``` > On Feb 1, 2016, at 11:52 AM, Chris Pike <[email protected]> wrote: > > B and C run successfully, but JVM has problems exiting when they are done, is > this normal behaviour? > > B. [info] summary + 3624 in 23s = 159.9/s Avg: 50 Min: 4 Max: > 481 Err: 0 (0.00%) Active: 10 Started: 10 Finished: 0 > [info] summary + 6376 in 29.2s = 218.0/s Avg: 42 Min: 3 Max: > 330 Err: 0 (0.00%) Active: 0 Started: 10 Finished: 10 > [info] summary = 10000 in 52s = 193.3/s Avg: 45 Min: 3 Max: > 481 Err: 0 (0.00%) > > C. [info] summary = 500 in 8.3s = 60.4/s Avg: 10 Min: 2 Max: > 104 Err: 0 (0.00%) > > Error after runs > > [info] The JVM should have exitted but did not. > [info] The following non-daemon threads are still running (DestroyJavaVM is > OK): > ... > Yes, it needs fixing, but haven’t gotten around to it…. speaking of fixing… the section in the readme needs to explain the usage better. e.g. how to modify the # of threads, iterations, warmup time, etc... Shawn
