Spring Cloud Stream, solace messages not going to error queue

@marc Thanks for the reply,

Yes, the client-username is the owner of the queue. Even when I go to Access Control -> Queues Owned, I see both MESSAGE.IN and MESSAGE.IN.DLQ. Regardless, the non-owner permissions are "Consume" for both.

This is the function throwing the exception. Notice it is the adapter function queue is binding to.

@Bean
@Throws(ContentNotFoundException::class)
fun adapter(): Function<Event, String> {
    return Function { event: Event ->

        throw ContentNotFoundException("Go to error queue");

    }
}

Nothing special about it, although I am wondering if Exception handling in Functions is different?

Looking around I don't see anything very different than a normal spring app... we're in the beginning of this project so there's not much to it besides sending messages across Solace.

These are my solace dependencies if that helps, is there any specific dependency that is needed for error handling?:

implementation("org.springframework.boot:spring-boot-starter")
implementation('org.springframework.boot:spring-boot-starter-integration:2.3.6.RELEASE')
implementation('org.springframework.integration:spring-integration-feed:5.3.4.RELEASE')

testImplementation('org.springframework.boot:spring-boot-starter-test')
testImplementation 'org.springframework.integration:spring-integration-test:5.3.4.RELEASE'

implementation ('com.solace.spring.cloud:spring-cloud-starter-stream-solace') {
    exclude group: 'org.springframework.boot', module: 'spring-boot-starter-cloud-connectors'
    exclude group: 'com.solace.cloud.cloudfoundry', module: 'solace-spring-cloud-connector'
    exclude group: 'com.solace.cloud.cloudfoundry', module: 'solace-java-cfenv'
    exclude group: 'io.pivotal.cfenv', module: 'java-cfenv-boot'
}
testImplementation 'org.springframework.cloud:spring-cloud-stream-test-support'
// JMS Solace
implementation 'com.solacesystems:sol-common:10.3.1'
implementation 'com.solacesystems:sol-jcsmp:10.3.1'
implementation 'com.solacesystems:sol-jms:10.3.1'
implementation 'javax.jms:javax.jms-api:2.0.1'
implementation 'com.sun.jndi:fscontext:1.2-beta-3'
implementation 'com.sun.jndi:providerutil:1.2'
implementation 'org.springframework:spring-jms:5.2.11.RELEASE'

Also, for more context, I believe the queues are connecting correctly, I see these logs on app boot:

c.s.s.c.s.b.p.SolaceQueueProvisioner     : Creating durable queue MESSAGE.IN for consumer group ADAPTER
c.s.s.c.s.b.p.SolaceQueueProvisioner     : Durable queue provisioning is disabled, MESSAGE.IN will not be provisioned nor will its configuration be validated
c.s.s.c.s.b.p.SolaceQueueProvisioner     : Testing consumer flow connection to queue MESSAGE.IN (will not start it)
c.s.jcsmp.impl.flow.BindRequestTask      : AD windowSize (255) is greater than router MaxDeliveredUnackedMessagesPerFlow (1), set AckThreshold to 0, folwId 56
c.s.s.c.s.b.p.SolaceQueueProvisioner     : Connected test consumer flow to queue MESSAGE.IN, closing it
c.s.s.c.s.b.p.SolaceQueueProvisioner     : Provisioning error queue MESSAGE.IN.DLQ
c.s.s.c.s.b.p.SolaceQueueProvisioner     : Error Queue provisioning is disabled, MESSAGE.IN.DLQ will not be provisioned nor will its configuration be validated
c.s.s.c.s.b.p.SolaceQueueProvisioner     : Testing consumer flow connection to queue MESSAGE.IN.DLQ (will not start it)
c.s.jcsmp.impl.flow.BindRequestTask      : AD windowSize (255) is greater than router MaxDeliveredUnackedMessagesPerFlow (1), set AckThreshold to 0, folwId 57
c.s.s.c.s.b.p.SolaceQueueProvisioner     : Connected test consumer flow to queue MESSAGE.IN.DLQ, closing it
o.s.c.stream.binder.BinderErrorChannel   : Channel 'MESSAGE.IN.ADAPTER.errors' has 1 subscriber(s).
o.s.c.stream.binder.BinderErrorChannel   : Channel 'MESSAGE.IN.ADAPTER.errors' has 2 subscriber(s).
c.s.s.c.s.b.i.JCSMPInboundChannelAdapter : Creating 2 consumer flows for queue MESSAGE.IN <inbound adapter b76f5678-3b32-4924-b62b-a835f56d8e94>
c.s.s.c.s.b.i.JCSMPInboundChannelAdapter : Creating consumer 1 of 2 for inbound adapter b76f5678-3b32-4924-b62b-a835f56d8e94
c.s.s.c.s.b.util.FlowReceiverContainer   : Binding flow receiver container 699eba3d-7771-4008-ac52-3bcb6fc1429e
c.s.jcsmp.impl.flow.BindRequestTask      : AD windowSize (255) is greater than router MaxDeliveredUnackedMessagesPerFlow (1), set AckThreshold to 0, folwId 58
c.s.s.c.s.b.i.JCSMPInboundChannelAdapter : Creating consumer 2 of 2 for inbound adapter b76f5678-3b32-4924-b62b-a835f56d8e94
c.s.s.c.s.b.util.FlowReceiverContainer   : Binding flow receiver container 8df4350c-8e2d-4846-b248-80aa56d27293
c.s.jcsmp.impl.flow.BindRequestTask      : AD windowSize (255) is greater than router MaxDeliveredUnackedMessagesPerFlow (1), set AckThreshold to 0, folwId 59
c.s.s.c.s.b.p.SolaceQueueProvisioner     : Subscribing queue MESSAGE.IN to topic MESSAGE.IN
c.s.j.protocol.impl.TcpClientChannel     : Error Response (400) - Subscription Already Exists - Queue 'MESSAGE.IN' - Topic 'MESSAGE.IN'
c.s.s.c.s.b.p.SolaceQueueProvisioner     : Queue MESSAGE.IN is already subscribed to topic MESSAGE.IN, SUBSCRIPTION_ALREADY_PRESENT error will be ignored...

Is this AD windowSize message an issue at all?

Yeah, really interesting solution @kimmieer

It was an issue with the version numbers; after update, messages are successfully landing on dlq.

Thanks @marc