Hi @akg17,
This is likely how the Solace Binder handles the different communication models defined in Spring Cloud Stream. I wrote a lot more detail in section 3 of the Spring Cloud Stream - Beyond the Basics codelab but to get straight to the point here:
When you use a “group” with Spring Cloud Stream you are saying to follow the Consumer Group pattern. The Solace binder does this by creating a non-exclusive durable queue endpoint that subscribes to the topics requested.
When you do not include a group the Solace binder is creating a non-durable queue with the proper topic subscriptions.
Given the info above and your error my guess is that your client-profile does not have permissions to create a durable endpoint. You can check that in PubSub+ Manager.
