reducing the prefetch can ensure that a minimum of messages are locked in this way. There is a new AbortSlowConsumerStrategy destination policy on trunk(for 5.4) that does what you want, check out https://issues.apache.org/activemq/browse/AMQ-378 you will need to use the latest 5.4-SNAPSHOT to access it.
Find the test case @ http://fisheye6.atlassian.com/browse/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/broker/policy/AbortSlowConsumerTest.java?r=HEAD On 15 June 2010 14:18, Luis Matos <luf...@gmail.com> wrote: > > In case a consumer can't process a message but is still active, the > pre-fetched messages for that consumer get stuck on activemq. > > Is there no way to setup a consumer timeout, i.e., after some time activemq > "gives up" on that consumer and sends them to another consumer? > -- > View this message in context: > http://old.nabble.com/Does-a-timeout-exist-for-Consumers--tp28891212p28891212.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
