Optional
accessOptional
consumerEnable or disable the propagation of consumer acknowledgements (ACKs) received on the active replication Message VPN to the standby replication Message VPN. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is true
.
Optional
deadThe name of the Dead Message Queue (DMQ). Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is "#DEAD_MSG_QUEUE"
.
Optional
deliveryThe delay, in seconds, to apply to messages arriving on the Topic Endpoint before the messages are eligible for delivery. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is 0
. Available since 2.22.
Optional
eventOptional
eventOptional
eventOptional
maxThe maximum number of consumer flows that can bind. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is 1
.
Optional
maxThe maximum number of messages delivered but not acknowledged per flow. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is 10000
.
Optional
maxThe maximum message size allowed, in bytes (B). Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is 10000000
.
Optional
maxThe maximum message spool usage allowed, in megabytes (MB). A value of 0 only allows spooling of the last message received and disables quota checking. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is 5000
.
Optional
maxThe maximum number of message redelivery attempts that will occur prior to the message being discarded or moved to the DMQ. A value of 0 means to retry forever. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is 0
.
Optional
maxThe maximum time in seconds a message can stay in the Topic Endpoint when respectTtlEnabled
is "true"
. A message expires when the lesser of the sender assigned time-to-live (TTL) in the message and the maxTtl
configured for the Topic Endpoint, is exceeded. A value of 0 disables expiry. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is 0
.
Optional
msgThe name of the Message VPN.
Optional
permission?: MsgVpnTopicEndpointTemplate.permissionThe permission level for all consumers, excluding the owner. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is "no-access"
. The allowed values and their meaning are:
"no-access" - Disallows all access. "read-only" - Read-only access to the messages. "consume" - Consume (read and remove) messages. "modify-topic" - Consume messages or modify the topic/selector. "delete" - Consume messages, modify the topic/selector or delete the Client created endpoint altogether.
Optional
redeliveryEnable or disable message redelivery. When enabled, the number of redelivery attempts is controlled by maxRedeliveryCount. When disabled, the message will never be delivered from the topic-endpoint more than once. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is true
. Available since 2.18.
Optional
rejectEnable or disable the checking of low priority messages against the rejectLowPriorityMsgLimit
. This may only be enabled if rejectMsgToSenderOnDiscardBehavior
does not have a value of "never"
. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is false
.
Optional
rejectThe number of messages that are permitted before low priority messages are rejected. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is 0
.
Optional
rejectDetermines when to return negative acknowledgements (NACKs) to sending clients on message discards. Note that NACKs cause the message to not be delivered to any destination and Transacted Session commits to fail. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is "never"
. The allowed values and their meaning are:
"always" - Always return a negative acknowledgment (NACK) to the sending client on message discard. "when-topic-endpoint-enabled" - Only return a negative acknowledgment (NACK) to the sending client on message discard when the Topic Endpoint is enabled. "never" - Never return a negative acknowledgment (NACK) to the sending client on message discard.
Optional
respectEnable or disable the respecting of message priority. When enabled, messages are delivered in priority order, from 9 (highest) to 0 (lowest). Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is false
.
Optional
respectEnable or disable the respecting of the time-to-live (TTL) for messages. When enabled, expired messages are discarded or moved to the DMQ. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is false
.
Optional
topicA wildcardable pattern used to determine which Topic Endpoints use settings from this Template. Two different wildcards are supported: * and >. Similar to topic filters or subscription patterns, a > matches anything (but only when used at the end), and a * matches zero or more characters but never a slash (/). A > is only a wildcard when used at the end, after a /. A * is only allowed at the end, after a slash (/). Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is ""
.
Optional
topicThe name of the Topic Endpoint Template.
The access type for delivering messages to consumer flows. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is
"exclusive"
. The allowed values and their meaning are: