[
https://issues.apache.org/jira/browse/AMQ-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Shepherd updated AMQ-4621:
--------------------------------
Attachment: AMQFreezeTest-5.8.0.redhat-60029.zip
Another test should be fixed by this issue.
> Provide a polling SlowConsumerPolicy that uses LastAck time on a sub
> --------------------------------------------------------------------
>
> Key: AMQ-4621
> URL: https://issues.apache.org/jira/browse/AMQ-4621
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.8.0
> Reporter: Gary Tully
> Assignee: Timothy Bish
> Labels: abort, connection, consumer, policy, slowConsumers
> Fix For: 5.9.0
>
> Attachments: AMQ4621Patch.txt, AMQFreezeTest-5.8.0.redhat-60029.zip,
> kahaPendingMEssage-20130905.zip, kahaPendingMEssage-20130906.zip
>
>
> The existing AbortSlowConsumer policy is event driven. It depends on a
> consumer slow event that is triggered when the prefetch is reached and there
> are subsequent dispatches.
> With prefetch=0|1 there still needs to be throughput to determine that the
> consumer is slow so one message can be pending if there are no new messages
> to sent to the destination.
> Providing an alternative implementation that will periodically poll consumers
> for their last ack time will be more deterministic. The slow advisory may
> never fire, but the consumer will get aborted if it does not ack in a timely
> manner.
> if lastAckTime exceeds the max and there are dispatched messages it can be a
> candidate for removal.
> Optionally lastAckTime exceeding and no dispatched messages can be a way to
> remove idle consumers. Not sure if that is necessary.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
