spring cloud stream producer setup
Hello solace community,
When I setup spring cloud stream integration, I end up getting below message when I try to publish. I see the default delivery mode is PERSISTENT.
Cannot send assured message: Assured message delivery is not enabled on this channel.
Is there any links talks about the configuration related to this?
Best Answer
-
Hi @Devakumar, the above fixes work if you don't want PERSISTENT (see this discussion of delivery modes). If you do want PERSISTENT the chances are you haven't turned on the correct permissions for the client profile:
0
Answers
-
Hi, this issue has been raised before. I think it was resolved in the StackOverflow question:
https://stackoverflow.com/questions/36925314/how-to-not-send-an-assured-message-via-solace-jms
Do the suggestions there help?0 -
Hi @Devakumar, the above fixes work if you don't want PERSISTENT (see this discussion of delivery modes). If you do want PERSISTENT the chances are you haven't turned on the correct permissions for the client profile:
0 -
@amackenzie said:
Hi, this issue has been raised before. I think it was resolved in the StackOverflow question:
https://stackoverflow.com/questions/36925314/how-to-not-send-an-assured-message-via-solace-jms
Do the suggestions there help?@amackenzie : I see enabling QoS via JMS template. Similar option available in spring cloud stream or any way to enable Direct delivery mode in spring cloud integration?
0 -
@Devakumar said:
@amackenzie said:
Hi, this issue has been raised before. I think it was resolved in the StackOverflow question:
https://stackoverflow.com/questions/36925314/how-to-not-send-an-assured-message-via-solace-jms
Do the suggestions there help?@amackenzie : I see enabling QoS via JMS template. Similar option available in spring cloud stream or any way to enable Direct delivery mode in spring cloud integration?
@TomF said:
Hi @Devakumar, the above fixes work if you don't want PERSISTENT (see this discussion of delivery modes). If you do want PERSISTENT the chances are you haven't turned on the correct permissions for the client profile:@TomF : Thanks for the reply. Let me check it out.
0
