https://issues.apache.org/bugzilla/show_bug.cgi?id=54600
Bug ID: 54600
Summary: JMeter should not kill Remote Servers via client
"Remote Exit" commands
Product: JMeter
Version: 2.9
Hardware: All
Status: NEW
Severity: normal
Priority: P2
Component: HTTP
Assignee: [email protected]
Reporter: [email protected]
Classification: Unclassified
Description:
The client JMeter Run options, "Remote Start" and "Remote Start All" will start
a jmeter test run on a running remote JMeter grid node(s). However, the
"Remote Exit" and "Remote Exit All" options will kill the test run *AND* the
grid node process(es). Why would the JMeter client allow users to shutdown the
grid server nodes?
Initial setup:
1. Install JMeter server on 2 machines (nodes) (version 2.9) on Windows or
Linux servers.
2. Install JMeter client on a users (testers) machine (version 2.9).
3. Configure the client to run a simple jmeter test against the server nodes.
4. Verify that the Jmeter grid nodes are running (ps -ef|grep -w jmeter) and
watch the logs (tail -f jmeter-server.log).
Steps to Reproduce:
1. With the client GUI, load a simple jmeter test and use the command:
run->Remote Start All.
2. After the test completes, with the client GUI do the command: run->Remote
Exit All.
3. Verify that the Jmeter grid nodes are still running (ps -ef|grep -w jmeter).
Actual Results:
The remote grid node JMeter process(es) was killed.
Expected Results:
When a client user selects "Remote Exit All", it should kill the test run on
the remote server, but *NOT* the server process(es) under any circumstances.
Note:
- This behavior also exists on 2.3.4
- The Run options, "Remote Start" will NOT restart a remote server.
--
You are receiving this mail because:
You are the assignee for the bug.
