Skip to content
This repository has been archived by the owner on Dec 8, 2023. It is now read-only.

per-VU connection/connection management #24

Closed
swantzter opened this issue May 16, 2023 · 0 comments · Fixed by #27
Closed

per-VU connection/connection management #24

swantzter opened this issue May 16, 2023 · 0 comments · Fixed by #27

Comments

@swantzter
Copy link
Contributor

I'm trying to set up a test where I want to be publishing messages more like our real-life scenarios where say 100 connections are each publishing messages, but Amqp.start() seem to overwrite the connection globally meaning that I'll only be using the connection created by the last call to start?

I'd like to suggest that Amqp.start() returns a connection ID which can then be passed to the various functions to use that connection. For compat I'd suggest that the current behaviour is kept if no connection ID is included in the call

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant