But a consumer always binds to a queue which has a subsciption to the topic (in destination), right?
So this doesn’t work.
Is there a solution for this?
Thanks and best regards
Mike
Hi @Mike13,
Currently the Solace Spring Cloud Stream binder enforces an “opinionated view” where the queue name is dynamically created (or expected to be) as {prefix}{destination}.{group}. We have an enhancement open to allow for this opinion to be overridden, but in the meantime I think I have a solution for you.
I believe this should work for you:
Set a custom DMQ name that ends with .DMQ. For example’s sake, let’s use FOO.DMQ (Note you can set the DMQ on each queue using SEMP/cli/PS+ Mgr or set up an endpoint template that automatically adds it based on queue naming)
Split the DMQ on the . and have your Spring Cloud Stream Binding use the first part (FOO in our example) as the destination and set the group name to be the second part (DMQ in our example)
Disable automatic provisioning of the queue (assuming you already created the queue you want to consume from) & subscriptions
So your binding config would end up looking like this: