https://issues.apache.org/bugzilla/show_bug.cgi?id=55375
--- Comment #9 from Sebb <[email protected]> --- I don't see any point in applying a temporary fix. The GUI seems to remember the correct instance whilst it is active. i.e. it will run which ever is selected from the list. However, when the JMX is saved, only the name is stored. So when the JMX is reloaded, it cannot possibly know which one was previously selected. This is a fundamental problem for both GUI and non-GUI test runs. One way to fix this is to insist that controller names are unique. Another way would be to store the instance number. This could either be done for every case, or only done where there are multiple matches, or the instance number could default to the first (i.e. only store it if not the first or only instance). Requiring unique names would be more likely to break existing test plans, as the default names are not unique, so I now think it would be better to store an instance number. Making the instance default to 1 would reduce the number of test plans that needed to be updated. However it would make it more difficult to determine whether the choice was deliberate or accidental, unless the test plan version is also taken into account. So it might be better to insist that the instance number was always saved. The question then arises - what should JMeter do if the user adds another controller with the same name after the MC entry has been selected? -- You are receiving this mail because: You are the assignee for the bug.
