You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2006/08/09 09:54:23 UTC
[jira] Updated: (AMQ-850) add the ability to timeout a consumer to
prevent a bad, hung or unused consumer consumer from grabbing messages
[ https://issues.apache.org/activemq/browse/AMQ-850?page=all ]
james strachan updated AMQ-850:
-------------------------------
Summary: add the ability to timeout a consumer to prevent a bad, hung or unused consumer consumer from grabbing messages (was: add the ability to timeout a prefetch buffer to prevent a single consumer grabbing messages)
Description:
If a MessageConsumer is created but not used, it still tends to get its prefetch-buffer worth of messages. If it does not process them within a specific time the consumer should either be closed, or the messages unacked and flushed from the buffer so that the consumer does not hog the messages.
Similarly if a consumer gets a message but then locks up without processing the message we should lazily kill the consumer releasing and redelivering all its messages
was:If a MessageConsumer is created but not used, it still tends to get its prefetch-buffer worth of messages. If it does not process them within a specific time the consumer should either be closed, or the messages unacked and flushed from the buffer so that the consumer does not hog the messages.
> add the ability to timeout a consumer to prevent a bad, hung or unused consumer consumer from grabbing messages
> ---------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-850
> URL: https://issues.apache.org/activemq/browse/AMQ-850
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Reporter: james strachan
> Fix For: 4.2
>
>
> If a MessageConsumer is created but not used, it still tends to get its prefetch-buffer worth of messages. If it does not process them within a specific time the consumer should either be closed, or the messages unacked and flushed from the buffer so that the consumer does not hog the messages.
> Similarly if a consumer gets a message but then locks up without processing the message we should lazily kill the consumer releasing and redelivering all its messages
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira