How to set Message TTL when using Spring Cloud Stream Binder Solace

Hi @FWinkler79 ,
I decided to make absolutely sure of this myself, so I ran Solace’s all-singing, all-dancing test harness, sdkperf (find it at the bottom of the downloads page). First, I put a message on my queue “test” with a very long TTL:
./sdkperf_java.sh -cip 127.0.0.1 -cu default@test -pql test -mtl 999999999 -mt persistent -mn 1.
Then, I put a message on the same queue with a TTL of 2s, flagged that it should be expired to the DMQ:
./sdkperf_java.sh -cip 127.0.0.1 -cu default@test -pql test -mtl 2000 -mt persistent -mn 1 -mdq
You’ll see that second message disappear after 2 seconds from test and appear on the DMQ.
Et viola!