Description:
Yes, the property Maxredelivery works even though there  is no receiver on the queue. If a message expires or has exceeded the value specified by the maxRedelivery property on a queue, the server checks the message’s JMS_TIBCO_PRESERVE_UNDELIVERED property. If JMS_TIBCO_PRESERVE_UNDELIVERED is set to "true", the server moves the message to the undelivered message queue $sys.undelivered. This undelivered message queue is a system queue that is always present and cannot be deleted. If JMS_TIBCO_PRESERVE_UNDELIVERED is set to "false", the message will be deleted by the server.

To make use of the undelivered message queue, the application that sends or publishes the message must set the boolean JMS_TIBCO_PRESERVE_UNDELIVERED property to "true" before sending or publishing the message. You can only set the undelivered property on individual messages. There is no way to set the undelivered message queue as an option at the per-topic or per-queue level.

You should create a queue receiver to receive and handle messages as they arrive on the undelivered message queue. If you want to remove messages from the undelivered message queue without receiving them, you can purge the $sys.undelivered queue with the administration tool, using the purge queue command described under Command Listing. You can also remove messages using the Administrative API included with TIBCO Enterprise Message Service. Note that $sys.undelivered ignores the global destination property setting. Messages in the undelivered message queue are not routed to other servers.


Symptoms:

Cause: