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

I'm not able to create a subscription topic under '#telemetry-trace' queue. How can I do it?

Aishwarya
Aishwarya Member Posts: 6 ✭
in General Discussions #1

I'm using open-telemetry framework. I have created a queue named '#telemetry-trace'. Now I'm trying to create a subscription topic for that queue and I'm getting an error 'The #telemetry-trace queue may not be configured'

Does anyone know how to solve this error?

Thanks in Advance!

Tagged:

Best Answers

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

    Hi @Aishwarya,

    # is used to specify reserved internal queues for Solace and you should not start your queue name with a # . Please change your queue name :)

    From the docs:

    <name> is a queue name of up to 200 characters (only reserved queue names can begin with # and invalid characters are '<>*?&;)


  • marc
    marc Member, Administrator, Moderator, Employee Posts: 963 admin
    #3 Answer ✓

    Hi @Aishwarya,

    I don't know exactly what it is off the top of my head but it looks like some sort of permissions or feature not enabled issue. Check that rest messaging is enabled and that your client-profile can send to that topic (ACL) as a starting point.

    If that doesn't resolve it please make a new post since this is a different issue than the original in this thread. I will be OOO for the next few weeks and that will get fresh eyes on the issue.

    Hope that helps!

Answers

  • marc
    marc Member, Administrator, Moderator, Employee Posts: 963 admin
    #4 Answer ✓

    Hi @Aishwarya,

    # is used to specify reserved internal queues for Solace and you should not start your queue name with a # . Please change your queue name :)

    From the docs:

    <name> is a queue name of up to 200 characters (only reserved queue names can begin with # and invalid characters are '<>*?&;)


  • Aishwarya
    Aishwarya Member Posts: 6 ✭
    #5

    Hello @marc Thank you so much for your help :)

  • Aishwarya
    Aishwarya Member Posts: 6 ✭
    #6

    Now I'm stuck with new issue:

    <solace-error-response>

      <code>403</code>

      <reason>

        <![CDATA[Unauthorized]]>

       

      </reason>

      <detail>

        <![CDATA[

    SMF ClientCtrl response error

    ]]>

       

      </detail>

      <internal-use>2:13503</internal-use>

    </solace-error-response>


    I'm trying to send messages through postman. But failed to do so.


    Do you have some ideas ?

  • marc
    marc Member, Administrator, Moderator, Employee Posts: 963 admin
    #7 Answer ✓

    Hi @Aishwarya,

    I don't know exactly what it is off the top of my head but it looks like some sort of permissions or feature not enabled issue. Check that rest messaging is enabled and that your client-profile can send to that topic (ACL) as a starting point.

    If that doesn't resolve it please make a new post since this is a different issue than the original in this thread. I will be OOO for the next few weeks and that will get fresh eyes on the issue.

    Hope that helps!

  • Aishwarya
    Aishwarya Member Posts: 6 ✭
    #8

    Hey @marc,

    Thank you so much for your help. It was an issue of permissions.

    Now it's working fine :)

    Kind Regards,

    Asishwarya.

Categories

This Month's Leaders

This Week's Leaders