This documentation is for WSO2 Message Broker 3.0.0. View documentation for the latest release.
Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.
Skip to end of metadata
Go to start of metadata

When using message queues in WSO2 Message Broker, messages are removed from the message store when the message consumers acknowledge the messages were received. There are several acknowledgement models defined in JMS specification 1.1

To configure the time within which consumers can acknowledge that messages were received, you can set the AndesAckWaitTimeOut entry in the JMS client:

System.setProperty("AndesAckWaitTimeOut", "30000");

If the acknowledgement fails within this time, the client informs the MB sever that this message was rejected from the client. The message is then scheduled to be redelivered later by the server. If you want to limit the number of times the message broker attempts to redeliver the message, you can set the maximumRedeliveryAttempts entry in the broker.xml file:

<!--Broker will drop the message after the configured number of delivery attempts for each message.-->
	    <maximumRedeliveryAttempts>10</maximumRedeliveryAttempts>

Note that the above configuration specifies the total number of attempts to redeliver the message after the original delivery attempt. For example, when the first attempt to send the message fails, there will be another 10 attempts to redeliver the message. After the maximum number of attempts to redeliver the message are breached, the message is sent to the Dead Letter Channel. This is useful when the client application does not acknowledge the message because an operation on the message failed.

If the message is successfully delivered on a redelivery attempt, the JMSRedelivered field is set to 'true' in the message header, allowing the client to determine whether the message was delivered on its original attempt or on a redelivery attempt.

  • No labels