🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

Spring Cloud Stream msgTtl on producer/supplier binding

Mike13
Mike13 Member Posts: 29 ✭
in General Discussions #1

Hi there
I tried this:

spring.cloud.stream.bindings.bookSupplierV1-out-0.destination=v1/bookJson
spring.cloud.stream.bindings.bookSupplierV1-out-0.binder=solace1

This works.
But when I do this in addition:

spring.cloud.stream.solace.bindings.bookSupplierV1-out-0.producer.msgTtl=23000

no message is sent to the destination.

The value in the SolaceProducerProperties is set to: 23000
This is also set:
xmlMessage.setTimeToLive(producerProperties.getMsgTtl());

public XMLMessage map(Message<?> message, SolaceProducerProperties producerProperties) {
XMLMessage xmlMessage = map(message);
xmlMessage.setDMQEligible(producerProperties.isMsgInternalDmqEligible());
if (producerProperties.getMsgTtl() != null) {
xmlMessage.setTimeToLive(producerProperties.getMsgTtl());
}
return xmlMessage;
}

Is this a bug or am I missing something?

Tagged:

Comments

  • marc
    marc Member, Administrator, Moderator, Employee Posts: 963 admin
    #2

    Hi @Mike13 ,
    Weird, it's working for me. Are you getting any sort of errors on app startup? I'm trying to think of a reason it wouldn't actually send the message. This what I did just to try it out in a simple app:

    Version info from pom

        <properties>
        <java.version>11</java.version>
        <solace-spring-cloud.version>1.1.1</solace-spring-cloud.version>
        <spring-cloud.version>Hoxton.SR8</spring-cloud.version>
    </properties>

    @SpringBootApplication
public class DemoApplication {

    public static void main(String[] args) {
        SpringApplication.run(DemoApplication.class, args);
    }

    @Bean
    public Supplier<String> supplier(){
        return () -> {
            System.out.println("Sending Hello World");
            return "Hello World";
        };
    }

    spring:
  cloud:
    function:
      definition: supplier
    stream:
      bindings:
        supplier-out-0:
          destination: output/test
      solace: 
        bindings:
          supplier-out-0:
            producer:
              msgTtl: 23000

    And then listening with sdkperf I can see the messages with the TTL set:

  • Mike13
    Mike13 Member Posts: 29 ✭
    #3

    Hi @marc
    I have not seen any error message.
    It seems like it works with one binder (Solace), but with two binders (Solace and Kafka), like we have in our test project, it doesn't work. I need to take a closer look at this...

  • marc
    marc Member, Administrator, Moderator, Employee Posts: 963 admin
    edited December 2020 #4

    Hey @Mike13, that's intriguing. Let me know what you find! I didn't have much time to look into it but I did quickly try using two solace binders in the same app and it continued working. Weird that for some reason using the Solace and Kafka binders together would act differently.

    As a heads up I'm going out on vacation for the holidays so if I don't get back to you in a timely manner that's why :)

Categories

This Month's Leaders

This Week's Leaders