activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-4621) Provide a polling SlowConsumerPolicy that uses LastAck time on a sub
Date Tue, 10 Sep 2013 10:15:53 GMT


Timothy Bish commented on AMQ-4621:

The fix I put in is: 272de3a146b602abe5f5679c6aca283af2be3d22

> Provide a polling SlowConsumerPolicy that uses LastAck time on a sub
> --------------------------------------------------------------------
>                 Key: AMQ-4621
>                 URL:
>             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,,,
> 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:

View raw message