DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
One additional property that would be of use here would be the consumption rate. If the topic reported the consumption rate this property could be used to define a threshold that the consumer must stay above.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<consumer>
<!-- The depth before which the policy will be applied-->
<depth>4235264</depth>
<!-- The message age before which the policy will be applied-->
<messageAge>600000</messageAge>
<!-- The number of message before which the policy will be applied-->
<messageCount>50</messageCount>
<!-- Policies configuration -->
<policy name="Delete">
<options>
<option name="delete-persistent" value="true"/>
</options>
</policy>
</consumer>
|
This <consumer> element will be added to the existing queue configuration to allow specific durable subscriptions to be identified and processed. In addition a new <topic> element will be added to allow configuration for topics. The resulting section of xml would look like this:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<topic key="stocks.us.*">
<consumer>
<!-- The depth before which the policy will be applied-->
<depth>4235264</depth>
<!-- The message age before which the policy will be applied-->
<maessageAge>600000</messageAge>
<!-- The number of message before which the policy will be applied-->
<messageCount>50</messageCount>
<!-- Policies configuration -->
<policy name="Delete">
<options>
<option name="delete-persistent" value="true"/>
</options>
</policy>
</consumer>
</topic>
|
...