You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by "MrZbb (via GitHub)" <gi...@apache.org> on 2023/04/15 13:10:15 UTC
[GitHub] [jmeter] MrZbb opened a new issue, #5804: only one BackendListener is effective
MrZbb opened a new issue, #5804:
URL: https://github.com/apache/jmeter/issues/5804
### 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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jmeter.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [jmeter] vlsi commented on issue #5804: BackendListener cannot have the same name
Posted by "vlsi (via GitHub)" <gi...@apache.org>.
vlsi commented on issue #5804:
URL: https://github.com/apache/jmeter/issues/5804#issuecomment-1594224090
I guess the solution here would be:
1) Implement https://github.com/apache/jmeter/pull/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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jmeter.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [jmeter] vlsi commented on issue #5804: BackendListener cannot have the same name
Posted by "vlsi (via GitHub)" <gi...@apache.org>.
vlsi commented on issue #5804:
URL: https://github.com/apache/jmeter/issues/5804#issuecomment-1578864054
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jmeter.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [jmeter] vlsi commented on issue #5804: BackendListener cannot have the same name
Posted by "vlsi (via GitHub)" <gi...@apache.org>.
vlsi commented on issue #5804:
URL: https://github.com/apache/jmeter/issues/5804#issuecomment-1578371291
@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?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jmeter.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [jmeter] pmouawad commented on issue #5804: BackendListener cannot have the same name
Posted by "pmouawad (via GitHub)" <gi...@apache.org>.
pmouawad commented on issue #5804:
URL: https://github.com/apache/jmeter/issues/5804#issuecomment-1578713074
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jmeter.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org