You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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
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.
Currently JMS Simulator can be configured with only one inbound queue or topic, how can I make it listen to multiple queues/topics?
The text was updated successfully, but these errors were encountered: