🎄 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.

Getting Caused by: com.solacesystems.jcsmp.InvalidOperationException: Cannot send assured message: A

ajinkyasagar
ajinkyasagar Member Posts: 24 ✭
in General Discussions #1

Is this issue with solace VPN or some properties needs to be set in spring config in application.yaml file?

Comments

  • ajinkyasagar
    ajinkyasagar Member Posts: 24 ✭
    #2

    Caused by: com.solacesystems.jcsmp.InvalidOperationException: Cannot send assured message: Assured message delivery is not enabled on this channel.


    this is error

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #3

    Hi @ajinkyasagar,

    This is an issue with broker configuration in all liklihood.

    1. Check your broker is enabled for guaranteed messaging. For instance, is the message spool shutdown?
    2. Check the client profile for the client username you are connecting with has guaranteed messaging enabled.
  • ajinkyasagar
    ajinkyasagar Member Posts: 24 ✭
    #4

    Issue got fixed it was broker permission issue for perticular user

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #5

    Ah good. It sounds like the client profile need to be changed. Glad you got it fixed, thanks for the feedback!

  • ajinkyasagar
    ajinkyasagar Member Posts: 24 ✭
    #6

    Client had both consumer and publisher role...same client was getting used to consume and publish message so there was issue with sequence of AD groups...when admin changed publisher as first group and consumer as second group ..then it worked..thanks for your input

Categories

This Month's Leaders

This Week's Leaders