Message VPN-level Message Spool Administration

You can perform the following Message VPN-level message spool administration tasks:

Changing the Starting Numbers for Sequenced Topics

This feature is deprecated and should not be used.

To change the default starting sequence number from 1 for sequenced topic subscriptions, enter the following commands:

solace(admin)# message-spool message-vpn <vpn-name>
solace(admin/message-spool)# sequenced-topic <topic> next-sequence-number <seq-num>

Where:

<topic> is the name of an existing sequenced topic

<seq-num> is the new sequence number in the range of 1 to 263 – 1

An INFO level Solace syslog event is generated whenever the sequence number is administratively changed. Administratively changing the sequence number to a value lower than the current next sequence number results in duplicate sequence numbers being issued. Likewise, changing it to a higher value results in a gap in sequence numbers. For information on how to create a sequenced topic subscription, refer to Message VPN-Level Guaranteed Messaging Configuration.

Deleting Messages

To delete one, some, or all spooled messages from a given Message VPN, enter the following Admin command:

solace(admin)# message-spool message-vpn <vpn-name>
solace(admin/message-spool)# delete-messages {{queue <queue-name>} | {topic-endpoint <te-name>}} [message <msg-id> [to <to-msg-id>]]

Where:

<queue-name> is the full name of the specified message queue, or part of the queue name with the wildcard character ? used to represent one character of the name, or the wildcard character * used to represent zero or more characters of the name, where entering only the wildcard character * for the name specifies all queues.

<te-name> is the full name of the specified topic endpoint, or part of the queue name with the wildcard character ? used to represent one character of the name, or the wildcard character * used to represent zero or more characters of the name, where entering only the wildcard character * for the name specifies all topic endpoints.

message <msg-id> specifies to delete the specified spooled message.

to <to-msg-id> specifies to delete a range of spooled messages starting from the message identifier specified by <msg-id> up to the message identifier specified by <to-msg-id>.

Example:

solace(admin)# message-spool message-vpn blue
solace(admin/message-spool)# delete-messages topic-endpoint solace21

Copying a Message From One Endpoint to Another

In some cases it may be useful to copy a single message from one endpoint (either a queue or a topic endpoint) to another endpoint, or from the replay log to an endpoint. For example, if the event broker moves a message to a dead message queue (DMQ) because an application is unable to consume the message, you can copy that message from the DMQ back to the original queue once the application issues have been resolved.

To copy a message from one endpoint to another, enter the following Admin command:

solace(admin)# message-spool message-vpn <vpn-name>
solace(admin/message-spool)# copy-message {source {{queue <queue-name>} | {topic-endpoint <te-name>} | {replay-log <replay-log-name>}}} {destination {{queue <queue-name>} | {topic-endpoint <te-name>}}} {message <replication-group-msg-id>}

Where:

<queue-name> is the full name of the specified message queue.

<te-name> is the full name of the specified topic endpoint.

<replay-log-name> is the name of the message replay log.

<replication-group-msg-id is the replication group message ID of the message you want to copy. A replication group message ID is an attribute of Solace messages, assigned by the event broker delivering the messages to the queue and topic endpoints, that uniquely identifies a message on a particular queue or topic endpoint within an HA group and replication group of event brokers.

Example: 

solace(admin)# message-spool message-vpn orange
solace(admin/message-spool)# copy-message source queue dmq1 destination queue q1 message rmid1:12eb1-a19b418311c-00000000-00000005