How to stop Default solace queue name getting created

Connectors & Integrations
1

Java 17, Spring boot - 3.0.13 and spring-cloud-starter-stream-solace:4.0.0

Our bindings are like below:

#Cloud stream channels configuration
spring:
  cloud:
    function:
      routing: enabled
      routing-expression: headers[‘type’]
      definition:
          routerFunc1;routerFunc2
    stream:
      default-binder: solace-broker
      bindings:
        routerFunc1-in-0:
          destination: QUEUE_NAME1
          group: QUEUE_GROUP
          provisionDurableQueue: false
          consumer:
            concurrency: 3
        routerFunc2-in-0:
          destination: QUEUE_NAME2
          group: QUEUE_GROUP
          provisionDurableQueue: false
          consumer:
            concurrency: 3

#Topic subscriptions
      solace:
        bindings:
          routerFunc1-in-0:
            consumer:
              provisionSubscriptionsToDurableQueue: false
              provisionDurableQueue: false
              queueAdditionalSubscriptions: TOPIC_NAME1
              auto-bind-dlq: true
          routerFunc2-in-0:
            consumer:
              provisionSubscriptionsToDurableQueue: false
              provisionDurableQueue: false
              queueAdditionalSubscriptions: TOPIC_NAME2
              auto-bind-dlq: true
      binders:
        solace-broker:
          type: solace
          environment:
            solace:
              java:
                host: solace_host.com
                msgVpn: msg_vpn
                clientUsername: admin
                clientPassword: password
                connectRetries: -1

We are seeing after deployment of service

dynamic queue and its subcription getting created, which we are not expecting as below
scst/wk/QUEUE_GROUP/plain/QUEUE_NAME1
scst/wk/QUEUE_GROUP/plain/QUEUE_NAME2

Our solace migration is creating queue names as below in solace
QUEUE_NAME1.QUEUE_GROUP (inside subscription topic)
QUEUE_NAME2.QUEUE_GROUP (inside subscription topic)

Can you help us property or function which are helpful stopping these dynamic queues

@marc

2

Hi @durgesh_patkari Can you check out this blog, it delves into the exact requirement that you are looking for -

3

But can we pass Configurable value from profiled yaml

assume that like

queueNameExpression: ‘’‘$QUEUENAME_GROUPNAME_VARIABLE’‘’

dev.yaml

QUEUENAME_GROUPNAME_VARIABLE: QUEUE_NAME1.QUEUE_GROUP ?

so that queueNameExpression will be referring to QUEUE_NAME1.QUEUE_GROUP

4

For me below config doing trick

queueNameExpression: “‘${QUEUE_NAME}.’ + ‘${GROUP_NAME}’”