Is it applicable to turn on/off Respect TTL settings in queue via API (using C#)

alhung

Hi everyone,

as title, I would like to turn on/off the Respect TTL setting using C# due to I have multiple queues with the same topic for different systems, and not all of the queue has consumers.

For those queue without consumers, I hope I can turn on the Message Expiry/Respect TTL freely until there is consumer to digest the queued messages. Based on the design, I don't need to worry the queue size full issue.

Now I could create the queue using C#, like the following code: and defined the properties, but after that, I could not turn it off by CreateQueue function, may I know if there is function to change the properties or other method to turn on/off Respect TTL via API?

Please let me know, thank you very much.

EndpointProperties endpointProps = new EndpointProperties()
                {
                    Permission = EndpointProperties.EndpointPermission.Consume,
                    AccessType = EndpointProperties.EndpointAccessType.NonExclusive,
                    RespectsMsgTTL = true
                };
IQueue queue = ContextFactory.Instance.CreateQueue(queueName))

amackenzie

The APIs for creating queues across the various languages are not intended to be full management APIs.

Is it important for you to do this in your application? Respect TTL seems like something you would not change often.

A recommendation would be to use the PubSub+ Manager web interface to do this or, of you need to do this programmatically, via the SEMPv2 management REST API. They both require message VPN-level admin credentials to do so, not the same user you are using in your application.

amackenzie

The APIs for creating queues across the various languages are not intended to be full management APIs.

Is it important for you to do this in your application? Respect TTL seems like something you would not change often.

A recommendation would be to use the PubSub+ Manager web interface to do this or, of you need to do this programmatically, via the SEMPv2 management REST API. They both require message VPN-level admin credentials to do so, not the same user you are using in your application.

alhung

Hi @amackenzie

Thanks for your suggestion, using SEMPv2 REST API is a good option 🤩🤩