Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can JMS Simulator listen to multiple queues/topics? #47

Open
coding-yogi opened this issue Jan 25, 2019 · 3 comments
Open

How can JMS Simulator listen to multiple queues/topics? #47

coding-yogi opened this issue Jan 25, 2019 · 3 comments

Comments

@coding-yogi
Copy link

Currently JMS Simulator can be configured with only one inbound queue or topic, how can I make it listen to multiple queues/topics?

@svettwer
Copy link
Contributor

Hi!

Connecting to multiple queues or topics with one simulator instance is currently not possible. As the simulator is designed for one queue/topic, this would be a more complex change as far as I can see. What is your use case for this?

BR,
Sven

@svettwer svettwer added Type: Feature State: To discuss In case there are open questions concerning the issue labels Jan 27, 2019
@coding-yogi
Copy link
Author

I have kind of 100+ services, out of which I might need to simulate around 30+. I don't really wish to start 30+ simulators listening to different queues/topics.

Currently the way I am using SImulator is I have only Default Scenario , it's like a Global Scenario taking care of all my scenarios (as I didn't want to define lot of classes for every scenario). so I am OK to have all queues/topics pushing messages to Default Scenario

@svettwer
Copy link
Contributor

svettwer commented Feb 4, 2019

Hi!

Okay, it sounds like you don't want to simulate much logic from the 30+ services. The design scope of the simulator was to simulate really big APIs. In those cases it makes sense to have one simulator per business API. If you don't have much to simulate, this might be overhead.
So if it is possible for you to configure your systems to push to one specified test queue/topic and dispatch with a default scenario, you could do this. But I'd like to recommend to separate different concerns into different instances as soon as the scenarios become more complex.

BR,
Sven

@svettwer svettwer added READY Prio: Low and removed State: To discuss In case there are open questions concerning the issue labels Feb 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants