Thanks for sharing the links. I have gone through these posts.
Following is the configuration in my service (spring could stream with solace).
I have manually created 2 exclusive queues (queue0, queue1) and have subscriptions on these queues.
queue0 with subscriptions “scm/account/0/bal and scm/account/1/bal”
queue1 with subscriptions “scm/account/2/bal and scm/account/3/bal”
I am running two instances of the service and expecting the each instance to bind to 1 queue. But I am observing that the first instance which comes up binds to both the queues. All the messages on both the queues are being consumed by only this instance. I am still in the process of figuring out whats going wrong here. It would be great if you can help me understand whats going wrong here. Also wanted to understand if this feature is available to be used in conjunction with spring cloud stream.
I am using spring-cloud-stream-binder-solace 3.1.0
spring:
stream:
bindings:
process-in-0:
destination: queue0,queue1
group: my_consumer_group
consumer:
partitioned: true