[ https://issues.apache.org/activemq/browse/AMQ-850?page=comments#action_36740 ] Maxim Fateev commented on AMQ-850: ----------------------------------
I think ideal solution would include self adjusting prefetch buffer size. At the beginning it couild be 1 but then increased if consumer is so fast that it gets throttled by network latency. If it slows down prefetch size should srink as well. The idea is to maintain queueing time (after being dispatched but before delivered to consumer callback) minimal while not blocking consumer. > 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
