Unable to connect to existing solace queue instead trying to creating a new durable queue and fails

General Discussions
4

Hi @nbommidi,
Your configuration looks close to correct to me so a few things to check:

  1. What version of the cloud stream binder are you using? If using the latest you’ll want to use autoBindErrorQueue instead of autoBindDmq
  2. Since you are using that feature you’ll also want to add provisionErrorQueue: false
  3. If the disabling of provisioning is being properly read by the binder you should see logs that look something like this:
Creating durable queue scst/wk/SINK/plain/TEMPS.Q for consumer group SINK
Durable queue provisioning is disabled, scst/wk/SINK/plain/TEMPS.Q will not be provisioned nor will its configuration be validated

Note that this worked for me using the cloud-streams-sink sample in this repo with this config:

spring:
  cloud:
    function:
      definition: sink 
    stream:
      bindings:
        sink-in-0:
          destination: TEMPS.Q
          #The presence of "group" tells the binder to follow the "consumer group" pattern
          group: SINK
      solace:
        bindings:
          sink-in-0:
            consumer:
              #This adds a topic subscription w/ wildcards to the queue created with a name of TEMPS.Q.SINK above 
              queueAdditionalSubscriptions: sensor/temperature/>
              autoBindErrorQueue: true
              provisionDurableQueue: false
              provisionSubscriptionsToDurableQueue: false
              provisionErrorQueue: false