Contents

A message may get expired based on its Time To Live (TTL) value. For more information on how a message expires, refer Chapter 8: Message Expiry in Fiorano MQ Concepts Guide.

31.10.1 Purging Expired Messages in Queues

Expired messages in the queues can be cleaned up by setting the flag 'IsDbCleanupEnabled' to 'True', by default this is set to 'false'.

To configure this parameter, login through FMQ-JMX in Fiorano Studio. Navigate to JMXConnection > Fiorano > mq > ptp > PTPManager > QueueSubsystem > config. The parameter can be changed here. Refer to the screenshot shown below.

The changes need to be saved and server should be restarted. The frequency with which the server checks for expired messages is again configurable through the parameter CleanupInterval (defaults to 10 minutes). You can configure this value at Subsystem level or at destination levels.

Icon

The cleanup handler is not present for Topics. This is only available for Queues. For now, this has to be done manually by running a browser on to a topic which has expired messages piled up.
If a browser is made to run on a topic, all the expired messages will get cleaned up. You will need to write a Topic browser application which runs on a specific topic in a regular interval of time. Refer to the Message Browser sample located at $Fiorano_Home/fmq/samples/PubSub/MessageBrowser for writing a browser sample on Topics. Purging of the expired messages happens only when the server is in active state.

Copies of the expired messages in any of the destinations can be stored in a queue named SYSTEM_DEADMESSAGES_QUEUE. For more information on this queue, refer to Chapter 13: Dead Message Queue.

Adaptavist ThemeBuilder EngineAtlassian Confluence