Bug 51938 - ClientJMeterEngine can leave server in busy state
Summary: ClientJMeterEngine can leave server in busy state
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.5.1
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks: 43168
  Show dependency tree
 
Reported: 2011-10-03 11:14 UTC by Sebb
Modified: 2017-01-25 07:34 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sebb 2011-10-03 11:14:50 UTC 
ClientJMeterEngine can leave the server in a busy state if the run command fails.

This is because the configure phase sets the busy flag (active) which is normally reset by the end of a test.
Comment 1 Sebb 2011-10-03 12:30:05 UTC 
[I am working on this]
Comment 2 Sebb 2011-10-03 12:49:46 UTC 
It's currently quite difficult to trigger an error in runTest().
[The error was noticed when testing possible fixes for Bug 51937]
Comment 3 The ASF infrastructure team 2022-09-24 20:37:47 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2575