Message VPN-Level Guaranteed Messaging Configuration

To configure Guaranteed Messaging-related parameters for a Message VPN, or to provision durable endpoints on a Message VPN, enter the following CONFIG command.

solace(configure)# message-spool message-vpn <vpn-name>

The CLI is now at the Message Spool VPN CONFIG command level, from which you can perform the following tasks:

At this level you can also configure durable queue and topic endpoints, and set Dead Message Queues.

Configuring Message VPN Event Thresholds

To configure the thresholds that control when message spool-related events are generated for the given Message VPN, enter the following CONFIG command:

solace(configure/message-spool)# event

The CLI is now at a level at which you can configure the set and clear thresholds for various message spool events for the Message VPN.

For specific information on the available Message VPN-level message spool events and how to set the set and clear thresholds for generating those events, refer to refer to Configuring VPN Message Spool Event Thresholds.

Configuring the Max Number of Flows

You can configure the maximum number of egress and ingress flows that can be created on the given Message VPN.

Egress flows are Guaranteed message client consumer flows, and ingress flows are Guaranteed message client publisher flows.

  • Egress: To configure the maximum number of egress flows that can be created on the given Message VPN, enter the following CONFIG command: 
    solace(configure/message-spool)# max-egress-flows <value>

    Where:

    <value>is an integer value specifying the maximum number of consumer flows. The valid range is 0 to 200000.

    The no version of this command, no max-egress-flows, resets the value to the default.

  • Ingress: To configure the maximum number of ingress flows that can be created on the given Message VPN, enter the following CONFIG command: 
    solace(configure/message-spool)# max-ingress-flows <value>

    Where:

    <value> is an integer value specifying the maximum number of publisher flows. The valid range is 0 to 1000000.

    The no version of this command, no max-ingress-flows, resets the value to the default.

Configuring the Max Number of Endpoints

To configure the maximum number of queues and topic endpoints that can be created on the given Message VPN, enter the following CONFIG command:

solace(configure/message-spool)# max-endpoints <value>

Where:

<value> is an integer value specifying the maximum number of queues and topic endpoints. The valid range and default value depends on the type of event broker used.

The no version of this command, no max-endpoints, resets the value to the default.

Configuring the Max Number of Transactions

To configure the total maximum number of simultaneous transactions (both local transactions and transactions within XA transaction branches) allowed in the given Message VPN, enter the following CONFIG command:

solace(configure/message-spool)# max-transactions <value>

Where:

<value> is an integer value specifying the maximum number of transactions allowed for the given Message VPN. The valid range and default value depends on the type of event broker used.

The no version of this command, no max-transactions, resets the maximum number of transactions allowed for the specified Message VPN back to the default value.

Configuring the Max Number of Transacted Sessions

Transacted sessions enable client applications to group multiple Guaranteed message send and/or receive operations together in single, atomic units known as transactions. Each transacted session can support a single series of transactions.

To configure the maximum number of simultaneous transacted sessions and/or XA Sessions allowed for the given Message VPN, enter the following CONFIG command:

solace(configure/message-spool)# max-transacted-sessions <value>

Where:

<value> is an integer value specifying the maximum number of transacted sessions allowed for the given Message VPN. The valid range and default value depends on the type of event broker used.

The no version of this command, no max-transacted-sessions, resets the maximum number of transacted sessions allowed for the specified Message VPN back to default.

Configuring the Max Spool Usage

To configure the maximum amount of the system-level message spool disk space that a given Message VPN can use, enter the following CONFIG command:

solace(configure/message-spool)# max-spool-usage <size>

Where:

<size> is an integer specifying the maximum amount of message spool disk space (in MB) the Message VPN can use. The valid range is from 0 to the maximum amount of message spool disk space supported for the entire system. The default value is 0.

For information about the default values for this setting, see Maximum Spool Usage.

We recommend that this value be at least the total of the worst-case spool size for messages queued to be delivered to clients plus the replay log's max-spool-usage. For more information about the replay log, see Configuring Message Replay.

The no version of this command (no max-spool-usage) resets the permitted message spool usage quota available for use by the Message VPN back to its default value.

No policing is done to ensure that the sum of all of the message spool quota allocated to Message VPNs does not exceed the event broker-wide message spool quota

Configuring Sequenced Topics

This feature is deprecated and should not be used.

A sequenced topic is a topic subscription for which any matching messages received on the Message VPN are assigned a sequence number that is monotonically increased by a value of one per message. To create a sequenced topic, enter the following CONFIG command:

solace(configure/message-spool)# sequenced-topic <topic>

Where:

<topic> is the name of the topic subscription to be sequenced in the form a/b/c. Default starting sequence number is 1.

The no version of this command, no sequenced-topic <topic>, deletes the sequenced topic, which disables the generation of sequence numbers.

  • To change the default starting sequence number from 1, refer to Changing the Starting Numbers for Sequenced Topics.
  • Sequenced topics are not supported by transacted sessions. Thus, any message to be sequenced that is also part of a transacted session does not have a sequence number applied; rather, the statistic “Transacted Message Not Sequenced” is incremented.
  • In the active/standby event broker redundancy model supported for Guaranteed Messaging, sequence numbers continue to increment seamlessly through event broker switch-overs.
  • In a multi-node network, where multiple event brokers are connected by Message VPN bridges, all publishers to a given sequenced topic must connect to the same event broker, otherwise duplicate sequence numbers result.