Hey @marc, I did see that disable note when I tried several options earlier. I used to get an invalid queue or permission issue. But now I did further analysis of all my properties in earlier trials as well.
The problem was that our predefined queue didn’t accept any prefix in the queue name, but the spring cloud binder configuration automatically add the prefix with all defaults and it resulted in an invalid queue.
I tried to use all the below properties as mentioned in the documentation at solace-spring-cloud/solace-spring-cloud-starters/solace-spring-cloud-stream-starter at master · SolaceProducts/solace-spring-cloud · GitHub
useDestinationEncodingInQueue =false
useGroupNameInQueueName=false
useFamiliarityInQueueName=false
I have observed the group name and familiarity name is removed from the prefix, but the encoding isn’t removed.
So I did a code review of the source code and realized that there is a typo in the property. The actual property should be useDestinationEncodingInQueueName
Now I am able to fix the invalid queue issue.
You may have to advise your team to correct the documentation. Sorry, I didn’t set it up to fix it.