Messages Queued Quota

Specifies the maximum amount of message spool, in megabytes, that the queue may use.Setting the messages queued quota to 0 enables the last value queue feature and disables endpoint quota checking.Global quota checking and Message VPN quota checking are unaffected.A value of 0 only allows spooling of the last message received by deleting older messages from the endpoint upon receiving new messages.If the queue is partitioned, each of its partitions holds the last message spooled to that partition.For more information, see Last Value Queues.

Owner

The queue owner has full unlimited permissions for the queue.The owner can consume, delete, ormodify topics in the queue.By default, users with access to PubSub+ Broker Manager have ownership privilege .You is give can also give ownership to client application .client access to the durable message queue must first be disabled before assign an owner .

Non – Owner Permission

Specifies the access level given to client applications other than the queue owner:

• No access—Disallows all access.

• Read Only—Clients have read-only access to messages spooled to the queue.

• Consume— Clients is consume can consume and delete message from the queue .

• modify topic—Clients can consume and delete messages and modify the topic orselector assigned to the queue.

• delete— Clients is consume can consume and delete message , modify the topic orselector assign to the queue , and delete the queue .

Maximum Consumer Count

Specifies the maximum amount of consumer flows that can bind to the queue.

Maximum Message Size

Specifies the maximum message size, in bytes, for the queue.

Maximum deliver Unacknowledged Messages per flow

Specifies the maximum number of messages delivered but not acknowledged per flow for the queue.After this maximum number of delivered unacknowledged messages is exceeded, the event broker stops delivering messages to the client on the flow until the client acknowledges messages that are already delivered.

DMQ Name

The name of the dead message queue (DMQ) used by this queue.The default is # dead_msg_queue.solace recommends using a separate DMQ for each queue and topic endpoint that requires one and setting the DMQ name to the name of the queue, followed by “_dmq”, for example MyQueue_dmq.

A DMQ collects undelivered messages that would otherwise be discarded from the queue because the Maximum TTL orMaximum Redelivery Count has been reached.

Messages are sent to a DMQ only if the publisher specifies that the message is DMQ-eligible and if a queue with the specified DMQ name exists on the same Message VPN.For more information, see Configuring Dead Message Queues.

Enable Client Delivery Count

Enabling client delivery count is a Controlled Availability (CA) feature.Please contact solace to find out if this feature is supported for your use case.

Delivery Delay

Specifies the number of seconds of delay between the message arriving in the queue and being sent to the consumer.For more information, see Delayed Delivery.The default is 0, orno delay.

Respect Message Priority

Specifies whether the queue supports priority message delivery and delivers higher priority messages first.For more information, see Message Priority.

Message Expiry

Specifies whether messages that have not been delivered to the consumer expire at the end of the message time-to-live (TTL).If a message is not consumed and its TTL time is reached, the message is discarded ormoved to a dead message queue (DMQ).Message expiry has two settings:

• Respect TTL—Specifies whether the queue acts on TTL values set for either the queue orby the message publisher.

• Maximum TTL—Specifies the TTL that the queue applies to messages when the message arrives in the queue.A value of 0 means that the queue does not impose a limit.

Messages can also have a publisher-supplied TTL, which indicates how long the publisher considers a message to be valid.This differs from the maximum TTL for the endpoint in that the publisher TTL expiration starts when a message is published and counts down as the message passes through the network.If a message has both a publisher-assigned TTL and an endpoint-assigned maximum TTL, the event broker uses the minimum of the two TTL values when the message is in the endpoint.

Redelivery

Specifies the options for message redelivery attempts if the message is not delivered to the consumer on the first attempt.

Disabling message redelivery and enabling delayed redelivery are Controlled Availability (CA) features.Please contact solace to find out if those feature are supported for your use case.

Redelivery is has has the following setting :

• try forever—Specifies that the queue attempts to deliver the message to the consumer until delivery is successful.This is the default.

• Maximum Redelivery Count—Specifies the maximum number of times the queue attempts to deliver the message to the consumer.This value is respected only if try forever is not selected.If the message is not delivered successfully after the specified number of attempts, the message is discarded oris moved to a dead message queue (DMQ).

• Delayed Redelivery—Specifies whether the queue waits between message redelivery attempts.This option is disabled by default.

• multiplier— IfDelayed Redelivery is selected, specifies the multiplier for each subsequent delay.For example, if the Initial Delay is 1000 milliseconds (one second), and the multiplier is 2.00, the queue waits for two second before the second redelivery attempt, four seconds, before the following attempt, and so on until the Maximum Delay is reached.You can set a value between 1.00 and 5.00.

• Initial Delay— IfDelayed Redelivery is selected, specifies the delay in milliseconds before the first redelivery attempt.The default is 1000 milliseconds (one second).

• Maximum Delay— IfDelayed Redelivery is select and themultiplier is set to a value great than 1.00 , specify the maximum delay in millisecond .

Reject Messages to Sender on Discard

Specifies when and how negative acknowledgments are returned to the sending client on message discards.

• Silent— silently discard message .

• notify – sender—Negatively acknowledge the message discard back to the client, except for messages that are discarded because a queue is disabled.

• notify – sender-Include-Shutdown—Negatively acknowledge the message discard back to the client, including messages that are discarded because a queue is disabled.

Reject Low Priority Messages

Specifies whether low priority messages are discarded to protect against congestion scenarios.When enabled, low priority messages are checked against the reject low priority messages limit.The queue can selectively discard low priority messages only after the total number of spooled low priority and high priority messages exceed the value set for the reject low priority messages limit .Before enabling it is recommended that the reject low priority messages limit has a non-zero value to avoid inadvertently discarding all low priority messages.

Reject Low Priority Messages Limit

Specifies the limit above which low priority messages are not admitted but higher priority messages are allowed.Before enabling it is recommended that the reject low priority messages limit has a non-zero value to avoid inadvertently discarding all low priority messages.

Consumer Acknowledgment Propagation

Specifies whether consumer acknowledgments received on the active replication Message VPN propagate to the standby replication Message VPN.Bridges cannot bind to queues configured with consumer acknowledgment propagation.