# maxRedelivery

The `maxRedelivery` property specifies the number of attempts the server should make to deliver a message sent to a queue.

Set maxRedelivery using the form:

       maxRedelivery=count

where count is an integer between 2 and 255 that specifies the maximum number of times a message can be delivered to receivers. A value of zero disables `maxRedelivery`, so there is no maximum.

Once the server has attempted to deliver the message the specified number of times, the message is either destroyed or, if the `JMS_TIBCO_PRESERVE_UNDELIVERED` property on the message is set to true, the message is placed on the undelivered queue so it can be handled by a special consumer. See Undelivered Message Queue for details.

For messages that have been redelivered, the `JMSRedelivered` header property is set to true and the `JMSXDeliveryCount` property is set to the number of times the message has been delivered to the queue. If the server restarts, the current number of delivery attempts in the `JMSXDeliveryCount` property is not retained.

Note: In the event of an abrupt exit by the client, the `maxRedelivery` count can be mistakenly incremented. An abrupt exit prevents the client from communicating with the server; for example, when the client exits without closing the connection or when the client application crashes. If a client application exits abruptly, the EMS server counts all messages sent to the client as delivered, even if they were not presented to the application.
Copyright © Cloud Software Group, Inc. All rights reserved.