BackendListener cannot have the same name

[MrZbb]

Expected behavior

When I configured two BackendListeners with the same name in JMeter for load testing and checked the log, only one was effective. Then, after examining the source code as shown in the figure, I found that the backend listener client is initialized based on the name of the component. This results in this problem. I hope the official can fix it

Actual behavior

No response

Steps to reproduce the problem

configure two BackendListeners with the same name

JMeter Version

5.5

Java Version

1.8

OS Version

windows

[vlsi]

@pmouawad , I see BackendListener implements Remoteable. If I understand correctly, it means that in the distributed scenario, the agents would collect and pass the samples to the controller first. Only the controller node would send the data to the backend.

Is it really needed?
What if every agent would just send its data to the backend directly?

[pmouawad]

Hello @vlsi, yes your understanding is correct.
I think it is needed, as some implementations send percentiles, would they be meaningful if every agent sends a value based on its subset ?
It does not concern all backendclient implementations but at least the InfluxDB one (not the Raw one) and the Graphite one.

[vlsi]

The question was to get better understanding.

However, I belive there might be value in different backend sending their own data with the corresponding label. Then the users will be able to tell if different load generators produce the same results or not.

[vlsi]

I guess the solution here would be:

1. Implement Add NoThreadClone#isShareable method so the elements can dynamically decide if they need cloning or not #5916
2. Teach RemoteListenerWrapper to return isShareable in case the source listener was shareable.

Then there will be no need to map listeners by their names as JMeter would propagate events to the appropriate listeners

3. Teach listener to send back the results directly without a controller process