5/3/2023 0 Comments Impact client binds(That is, only one flow can be active.) The first flow to bind to the queue can consume messages from it, and when that Flow disconnects, the next oldest Flow to bind becomes active and can begin receiving messages, and so on. Solace(configure/message-spool/queue)# access-type Įxclusive specifies that multiple subscriber flows established by clients can be bound to the queue, but only one flow out of all the bound flows is able to receive messages at a time. The client access type cannot be changed until client access to the durable message queue is disabled (refer to Enabling / Disabling Client Access to Queues). To configure the client access type for durable message queues on the Solace PubSub event broker on a per-queue basis, enter the following CONFIG command. In this topic we'll show you how to use the Solace CLI to configure the parameters and features associated with a durable queue. However, the queue cannot be deleted until it's shutdown, which disables client access to it (refer to Enabling / Disabling Client Access to Queues). The no version of this command, no queue, deletes the specified durable message queue from the Message VPN. A temporary queue differs from a durable queue provisioned through the Solace CLI or SolAdmin in that it's dynamically provisioned by a client application, and can only exist as long as the client is connected. The name for a temporary queue can be a maximum of 250 characters. Each queue name in a Message VPN must be unique. If the name contains a hierarchy of levels (for example, "a/b") each level of the hierarchy must contain one or more valid characters, and the name can't begin or end with a slash. is a queue name of up to 200 characters (only reserved queue names can begin with # and invalid characters are '*?
0 Comments
Leave a Reply. |